Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Search Issues

search_issues
Read-only

Search and list Sentry issues, including grouped errors, crashes, and user feedback, with status, occurrences, affected users, assignee, and first/last seen using natural language or Sentry query syntax.

Instructions

Search Sentry issues (grouped errors, crashes, and user feedback) and list them with status, occurrences, users impacted, assignee, and first and last seen. Accepts natural language or Sentry issue search syntax. For individual events, counts, or aggregates, use search_errors, search_logs, or search_traces.

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": "search_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNodate: last seen; freq: event count; new: first seen; user: user count; recommended: Sentry's priority ranking.date
freshNoBypass cached reads.
limitNoMaximum issues to return.
queryNoNatural language or Sentry issue search syntax, e.g. `is:unresolved level:error firstSeen:-24h assigned:me release:latest environment:production issue.priority:high issue.category:feedback userCount:>100`.is:unresolved
periodNoOnly issues with activity in this window.30d
regionUrlNo
projectSlugOrIdNoThe project slug or numeric ID.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.
includeExplanationNoReturn how the query was translated or repaired.

Output Schema

NameRequiredDescriptionDefault
urlYesOpens these results in Sentry.
notesYes
queryYes
issuesYes
explanationYes
executedSearchYes
presentationHintYes
suggestedActionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds useful behavior beyond that: the tool accepts either natural language or Sentry search syntax, and it returns a defined set of fields. The includeExplanation-style "query translated or repaired" behavior is only implied via the schema, and caching semantics (the `fresh` flag) are not mentioned in prose.

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 sentences, zero filler: the first front-loads what is returned, the second handles the routing question. Nothing repeats the tool name or title verbatim without adding 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 9 optional parameters, a high-coverage schema, and an output schema covering return shape, the description is complete enough to call the tool confidently. It stops short of mentioning the default unresolved-only scope, paging limits, or the meaning of `fresh`, though those are largely recoverable from the schema.

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 89%, so enum meanings, defaults, and the rich query-syntax example are already documented in structured data. The description only echoes the query-language flexibility ("natural language or Sentry issue search syntax") without adding parameter-level meaning, which is the expected baseline when the schema does the heavy lifting.

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 ("Search Sentry issues") and immediately disambiguates the domain by defining issues as "grouped errors, crashes, and user feedback." It then lists the returned attributes (status, occurrences, users impacted, assignee, first/last seen), so an agent knows exactly what this retrieves versus the event-level siblings.

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

Usage Guidelines5/5

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

Explicitly routes the agent away for the wrong granularity: "For individual events, counts, or aggregates, use search_errors, search_logs, or search_traces." This names alternatives and the condition that selects them, which is exactly the when-not guidance needed when several similarly named search tools coexist.

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