Skip to content

get_sentry_resource gives no guidance for Explore > Errors list URLs #2278

Open

Description

@sentry-junior

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: #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]

Activity

  1. linear-code commented on Nov 15, 2026

    @linear-code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    MCPSentry MCP tools, transports, and documentationmcp-feedback-pattern

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions