Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Issue Breadcrumbs

get_issue_breadcrumbs
Read-only

Retrieve the breadcrumb trail for a Sentry issue event, including navigation, console, HTTP, and user actions leading up to the error.

Instructions

Get the breadcrumb trail of a Sentry issue event: the navigation, console, HTTP, and user actions leading up to the error.

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_breadcrumbs"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
eventIdNoAn event ID in the issue, or `latest`.latest
issueIdNoThe issue short ID, e.g. `PROJECT-1Z43`.
issueUrlNoThe issue URL, e.g. https://my-org.sentry.io/issues/PROJECT-1Z43
regionUrlNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
eventIdYes
issueIdYes
breadcrumbsYesThe trail of events leading up to the error, oldest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results are scoped to a single issue event and lists the breadcrumb categories, but says nothing about caching (the `fresh` parameter's effect), result volume, or how breadcrumbs are ordered — context the annotations cannot supply.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the resource is named first and the returned content types follow immediately. Nothing could be removed without losing information.

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, return-value explanation is unnecessary, and annotations cover safety. The remaining gap is that all six parameters are optional and the description never says which identifier combination is required or that `latest` resolves to the newest event — helpful for a first call but not strictly missing given the schema text.

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 83%, so the schema already documents eventId (including the `latest` default), issueId, issueUrl, organizationSlug, regionUrl, and fresh. The description adds no parameter-level meaning at all, so baseline 3 applies rather than a higher score.

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

Purpose4/5

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

States a specific verb ('Get') and resource ('breadcrumb trail of a Sentry issue event') and enumerates the payload categories (navigation, console, HTTP, user actions) leading up to the error. That makes it distinguishable from data-oriented siblings like get_issue_details or get_event_stacktrace, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 'leading up to the error' signals a debugging/reproduction context, but there is no explicit when-to-use, when-not-to-use, or pointer to sibling tools that also surface event-level data. An agent must infer the selection criteria.

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