Get Sentry Resource
get_sentry_resourceFetch Sentry issues, events, traces, replays, monitors, dashboards, snapshots, or conversations by URL or ID; the resource type is detected from the URL.
Instructions
Fetch a Sentry resource by URL or ID: issues, events, traces, spans, agent conversations, replays, monitors, metric alerts, dashboards, preprod snapshots, and snapshot images. Start here for any Sentry URL or issue, event, trace, or replay ID; the type is detected from the URL. To list agent conversations, use search_agent_conversations.
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_sentry_resource"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| url | No | A Sentry URL. The resource type is detected from it. | |
| fresh | No | Bypass cached reads. | |
| issueId | No | ||
| issueUrl | No | ||
| resourceId | No | The ID for the resource type: issue short ID (e.g. `PROJECT-123`), event, trace, replay, or conversation ID, monitor slug, dashboard ID or exact title, or snapshot artifact ID. Required without a URL. | |
| resourceUrl | No | ||
| packageNames | No | Exact, case-sensitive package names recorded on the event. Returns their versions. Only for an event URL or the `event` type. | |
| resourceType | No | Required without a URL. With a URL, `trace` widens a span URL to its whole trace. `ai_conversation` is a gen_ai.conversation.id; `snapshot` is a preprod snapshot. | |
| organizationSlug | No | The organization slug, from `find_organizations`. In `org/project` notation, the part before the slash. |