Get Issue Details
get_issue_detailsRetrieve 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
| Name | Required | Description | Default |
|---|---|---|---|
| fresh | No | Bypass cached reads. | |
| eventId | No | The 32-character hex event ID. | |
| issueId | No | The issue short ID, e.g. `PROJECT-1Z43`. | |
| issueUrl | No | The issue URL, e.g. https://my-org.sentry.io/issues/PROJECT-1Z43 | |
| regionUrl | No | ||
| packageNames | No | Exact, case-sensitive package names recorded on the event. Returns their versions. Requires eventId. | |
| organizationSlug | No | The organization slug, from `find_organizations`. In `org/project` notation, the part before the slash. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| seer | Yes | ||
| event | Yes | ||
| issue | Yes | ||
| replays | Yes | ||
| sideQuests | No | Optional setup fixes and follow-ups, most useful first. Not needed for the current task. | |
| codeLocation | Yes | ||
| relatedIssues | No | Up 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. | |
| suspectCommit | Yes | ||
| externalIssues | Yes | ||
| aiConversations | Yes | ||
| suggestedActions | Yes |