get_sentry_resource gives no guidance for Explore > Errors list URLs

Open
  • Is something wrong?
#2,278 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@sentry-junior is already working on this.

Since Nov 15, 2026.

  • #2279 by @sentry-junior — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
32/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript
Domain
tooling

Research direction

Read packages/mcp-core/src/tools/catalog/get-sentry-resource.ts: parseSentryUrl returns unknown for /explore/errors/... paths, and UNSUPPORTED_URL_GUIDANCE (~:93-114) has no errors/Discover entry, so resolveFromParsedUrl throws at ~:265-268. Follow an existing entry (issue lists, alerts) as the shape for a new errors-list entry that points callers at search_errors and spells out the project, environment, statsPeriod/start/end and query params. Done means the weekly-report URL produces that guidance instead of the generic error, with a test alongside the other URL-parsing tests. Check draft PR #2279 first — it may already cover this.

Written by the indexing model from the issue text.

Description

MCP mcp-feedback-pattern

Pattern: get_sentry_resource called with an Explore > Errors (Discover) list URL, such as the "view in Sentry" link in the weekly report email (/explore/errors/homepage/?dataset=errors&...&referrer=weekly_report), returns the generic "Could not determine resource type from URL" error. It doesn't say to use search_errors, and it drops the page's project and time scope, so the caller rebuilds them with other search tools.

Reports: 1 (Sentry MCP user feedback MCP-SERVER-GQE, opencode caller, server 0.42.0, kind=missing, impact=worked_around).

What happens

  1. The caller passes url=https://<org>.sentry.io/explore/errors/homepage/?field=title&...&dataset=errors&sort=-timestamp&referrer=weekly_report&project=... (sampled tools/call get_sentry_resource span, status error).
  2. parseSentryUrl returns unknown for this path. UNSUPPORTED_URL_GUIDANCE (packages/mcp-core/src/tools/catalog/get-sentry-resource.ts:93-114 at 2884bc6) has entries for API URLs, issue lists, alerts, logs and traces, but none for errors/Discover pages, so resolveFromParsedUrl throws the generic message (:265-268).
  3. These are real Sentry routes: getsentry/sentry static/app/router/routes.tsx mounts discoverErrorsChildren (index, homepage/, queries/, results/) under explore/errors/, explore/discover/ and the legacy /discover/, and static/app/views/discover/pathnames.tsx builds Discover links on explore/errors.

Fix: getsentry/toolkit#2279 (draft) adds an errors-list entry that points at search_errors, and lists the page's project, environment, statsPeriod/start/end and query params in the guidance so the caller can carry the scope over.

Not this issue: event-detail URLs under explore/errors/<project>:<eventId>/, and explore/agents/ conversation URLs, aren't covered here.

via automation evt_905b9c478746fd9deeb853f85ad7441b · Run ID dispatch_a156216a8080465c06ac0c79b49960ca.

--

View Session [Sentry]

Dominant language
TypeScript
Stars
961
Forks
179
Avg merge
15h 33m
Merged PRs (30d)
476

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/toolkit

All issues in getsentry/toolkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.