Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Search Issue Events

search_issue_events
Read-only

Search and filter individual events within a Sentry issue, newest first, by environment, release, user, trace, or time using natural language or Sentry event search syntax.

Instructions

Search and filter the individual events (occurrences) of one Sentry issue, newest first, by environment, release, user, trace, or time. Accepts natural language or Sentry event search syntax. Use search_issues to search across 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": "search_issue_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort for the Sentry link only, e.g. `-timestamp`; returned events are always newest first.
freshNoBypass cached reads.
limitNoMaximum events to return.
queryNoNatural language or Sentry event search syntax, e.g. `environment:production release:1.0.0 user.email:alice@example.com trace:<id>`.
periodNoRelative time window, e.g. `30m`, `24h`, `7d`, `90d`.
issueIdNoThe issue short ID, e.g. `PROJECT-123`. Give this or issueUrl.
issueUrlNoThe Sentry issue URL.
regionUrlNo
projectSlugNoThe project slug. Helps translate project-specific tags.
organizationSlugNoThe organization slug, from `find_organizations`. Not needed with an issue URL.
includeExplanationNoReturn how the query was translated or repaired.

Output Schema

NameRequiredDescriptionDefault
urlYesOpens these results in Sentry.
notesYes
queryYes
eventsYesNewest first; the issue events endpoint has no sort.
issueUrlYes
explanationYes
executedSearchYes
presentationHintYes
suggestedActionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/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 genuinely new behavioral context beyond them: results are always newest first, and the tool accepts either natural-language or Sentry search syntax. It does not mention permissions or rate limits, but with annotations present that gap is minor.

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?

Three tight sentences: purpose and scope first, then query-language capability, then the sibling routing. Every sentence carries information and nothing is redundant.

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?

For an 11-parameter tool with an output schema covering return values, the description conveys the essentials: subject, ordering guarantee, accepted query language, and the alternative tool. The main omission is that no parameter is formally required even though issueId or issueUrl is needed in practice, which the description never surfaces.

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 91%, so the schema already documents all 11 parameters including query syntax examples and the issueId/issueUrl alternative. The description's list of filter facets (environment, release, user, trace, time) largely restates what the query parameter schema already shows, so it adds little beyond the baseline.

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 and filter the individual events (occurrences) of one Sentry issue"), scopes it to a single issue, and names the sibling it is not (search_issues). An agent can distinguish it from search_issues and search_errors without opening either 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?

The final sentence gives explicit routing: "Use search_issues to search across issues," which tells the agent when the sibling is the better choice. It also explains that both natural language and Sentry event search syntax are accepted, though it does not state that issueId or issueUrl is effectively required for a meaningful call.

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