Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Issue Details

get_issue_details
Read-only

Retrieve Sentry issue details by ID, URL, or event, including title, status, counts, stacktrace, root cause, suspect commit, linked tickets, replays, and package versions.

Instructions

Get the details of one Sentry issue, by issue ID, URL, or event ID: title, status, counts, the latest or a chosen event with its stacktrace, Seer root cause, suspect commit, linked tickets, and replays. Can also return installed package versions for one event. Use search_issues to list issues.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_issue_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
eventIdNoThe 32-character hex event ID.
issueIdNoThe issue short ID, e.g. `PROJECT-1Z43`.
issueUrlNoThe issue URL, e.g. https://my-org.sentry.io/issues/PROJECT-1Z43
regionUrlNo
packageNamesNoExact, case-sensitive package names recorded on the event. Returns their versions. Requires eventId.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
seerYes
eventYes
issueYes
replaysYes
sideQuestsNoOptional setup fixes and follow-ups, most useful first. Not needed for the current task.
codeLocationYes
relatedIssuesNoUp to 5 other issues related to this one, most relations first: similar_stacktrace (likely duplicate), same_trace (same request), contributing (behind a metric alert). Check them before resolving or ignoring this issue.
suspectCommitYes
externalIssuesYes
aiConversationsYes
suggestedActionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered; the description adds that the tool resolves a single issue from three different identifier types and that it can surface derived analysis (Seer root cause, suspect commit) and per-event package versions. It omits that zero parameters are strictly required and what happens if identifiers are mixed or missing, which is meaningful behavioral detail for a resolver-style tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the verb and resource, then the payload, then the redirect to the sibling. The field enumeration is long but each item helps an agent decide whether this tool has what it needs; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the description needn't spell out return shapes, and annotations cover the safety profile, so the remaining burden was identity-selection rules. Those are only partially addressed (issue IDs vs URLs vs event IDs are named but not prioritized, and the all-optional parameter set is unexplained), leaving a small but real gap for a 7-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 86%, so all seven parameters are already documented, and the description mostly echoes that ('by issue ID, URL, or event ID', 'package versions for one event'). It adds the useful framing that the three identifiers are alternative ways to reach the same issue, but no format or exclusivity rules beyond the schema — the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the details of one Sentry issue') and enumerates the payload (title, status, counts, latest/selected event with stacktrace, Seer root cause, suspect commit, linked tickets, replays), plus the accepted identifier forms. The final sentence explicitly separates it from search_issues, so an agent can pick between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative ('Use search_issues to list issues') and gives the condition selecting it, which is the most important routing decision among siblings. It does not state how to choose between issueId, issueUrl, and eventId, nor how this relates to narrower siblings like get_event_stacktrace or get_issue_activity — a gap, but context is clear overall.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.