selfhosted-sentry-mcp

merge_issues

Destructive

Combine error issues from the same project into a single issue after confirming they share a root cause. Cross-project merges are refused.

Instructions

Merge issues of the same project into one (error issues only; cross-project merges are refused). Sentry picks the surviving parent itself — the issue first seen earliest — which is not necessarily issue_id; the others become its children. The merge completes asynchronously in Sentry. Use after confirming the issues share a root cause.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issue_id": "<issue_id>",
      "target_ids": "<target_ids>"
    },
    "name": "merge_issues"
  }
}

Input Schema

Name	Required	Description	Default
`issue_id`	Yes	Numeric issue ID or short ID (e.g. PROJ-1A2)
`target_ids`	Yes	Other issues to merge with issue_id: numeric IDs or short IDs, same project (max 10).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

changedInput schema / properties / issue_id / description

Previous value: -"Primary issue ID to merge into."New value: +"Numeric issue ID or short ID (e.g. PROJ-1A2)"

changedInput schema / properties / target_ids / description

Previous value: -"Issue IDs to merge from (max 10)."New value: +"Other issues to merge with issue_id: numeric IDs or short IDs, same project (max 10)."

First observedv1.2.0Jul 12, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare destructive/non-idempotent/open-world; the description adds the operationally critical facts that Sentry picks the surviving parent itself (earliest first-seen, not necessarily issue_id), that the others become children, and that the merge completes asynchronously. These are non-obvious behaviors an agent could not infer from the schema or hints.

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, no redundancy. Scope restrictions come first, then the behavior of the merge, then the precondition — a sensible priority order for a destructive operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two well-documented parameters, no output schema, and a destructive hint, the description covers everything an agent needs: eligibility restrictions, async completion, parent-selection semantics, and the precondition. No meaningful gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description still adds real meaning: it clarifies that issue_id is not guaranteed to be the surviving parent, which reframes what the parameter actually controls. It does not restate formats already in the schema, keeping the addition purely additive.

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 + resource ('merge issues of the same project into one') and immediately narrows scope with two constraints: error issues only, cross-project merges refused. This distinguishes it cleanly from siblings like bulk_update_issues, which mutate status rather than consolidate issues.

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?

'Use after confirming the issues share a root cause' gives a clear precondition for invocation. It stops short of naming alternatives or stating when NOT to use it, so it is one step below fully explicit routing guidance.

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