Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Issue User Reports

get_issue_user_reports
Read-only

Retrieve legacy User Reports and crash-report feedback attached to a Sentry issue to see what users reported happened.

Instructions

Get the legacy User Reports and crash-report feedback attached to a Sentry issue: what users said happened. For User Feedback widget submissions, use search_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_user_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
limitNoMaximum user reports to return.
cursorNo
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
issueIdYes
reportsYes
nextCursorYesPass as cursor with the same issue scope for the next page.
organizationSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/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 real context beyond that by labeling the data 'legacy' and characterizing it as free-text user/crash feedback rather than structured issue fields. It does not mention caching behavior (implied only by the 'fresh' parameter), pagination, or volume of results.

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?

Two compact clauses, front-loaded with the resource and its scope, followed by the alternative. The colon gloss on 'what users said happened' earns its place by clarifying the payload type. No filler.

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?

An output schema exists and annotations carry the safety profile, so the description needn't explain return values or read-only semantics. It covers what is retrieved and when to use a sibling instead. Remaining gaps — pagination via cursor, cache behavior, and identifier requirements — are minor given the surrounding schema richness.

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?

The description names no parameters at all; all seven carry schema descriptions at roughly 71% coverage, so the schema does most of the work. A notable unresolved ambiguity is that zero parameters are required while the tool clearly needs an issue identifier and organization context — the description could have said which identifier form to prefer, but does not.

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 legacy User Reports and crash-report feedback on a Sentry issue) and glosses the payload as 'what users said happened'. It explicitly separates this data source from User Feedback widget submissions, letting an agent distinguish it from sibling issue tools without opening a 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?

Gives one explicit routing rule: widget submissions go to search_issues instead. That is a concrete condition selecting an alternative, which is more than most definitions offer. It stops short of a full when/when-not treatment, and says nothing about prerequisites such as needing an issue identifier or org context.

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