Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Find Related Issues

find_related_issues
Read-only

Finds Sentry issues related to a given issue, including likely duplicates by stack trace, errors in the same trace, and error issues behind a metric alert, so you can check links before resolving or ignoring it.

Instructions

Find Sentry issues related to an issue: likely duplicates with a similar stack trace in the same project, other errors in the same trace, and the error issues behind a metric alert. Returns each related issue with its status and why it's related. Use it before resolving or ignoring an issue. It doesn't compare titles or error messages.

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

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
limitNoMaximum related issues per relation type.
typesNoRelation types to return; all when omitted. similar_stacktrace: likely duplicates. same_trace: errors in the same trace, often the other side of a request. contributing: for a metric issue, the error issues behind it.
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
notesYes
issueIdYes
relatedIssuesYesIssues matched by more relation types first.
relationTypesYesWhether each requested relation type ran.
organizationSlugYes
suggestedActionsYes

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 by structured data. The description adds real value with what comes back ('each related issue with its status and why it's related') and by naming the relation taxonomy. It still does not mention caching behavior even though a `fresh` parameter exists, which is the one behavioral trait an agent would want disclosed 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?

Four tight sentences with zero waste: purpose and taxonomy first, the pre-resolve trigger second, the boundary condition last. No filler adjectives or redundant restatement of the tool name.

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, the description need not explain return values, and it correctly focuses on relation semantics and the intended moment of use. The main remaining gap is that all 7 parameters are optional and the description never says an issue identifier (issueId or issueUrl, plus organization) is effectively required, which matters for a tool that cannot run without a target issue.

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 coverage is 86%, so the schema already documents issueId, issueUrl, regionUrl, organizationSlug, limit and types, including the per-enum explanations of similar_stacktrace, same_trace, and contributing. The description's mention of 'likely duplicates with a similar stack trace' and 'error issues behind a metric alert' largely restates the schema's own type descriptions rather than adding new meaning. Baseline 3 applies where 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 ('Find Sentry issues related to an issue') and then enumerates the three concrete relation families it covers: likely duplicates via similar stack traces, other errors in the same trace, and the error issues behind a metric alert. It also draws a clear boundary ('doesn't compare titles or error messages'), which lets an agent distinguish this from a text-search sibling without opening any 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 an explicit when-to-use trigger: 'Use it before resolving or ignoring an issue,' which frames it as a pre-mutation safety check. The trailing negative ('doesn't compare titles or error messages') implicitly routes text-matching work elsewhere, but no sibling is named and no exclusion like 'do not use to browse all issues' is stated outright.

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