Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Unlink Issue

unlink_issue
DestructiveIdempotent

Remove a linked external ticket or GitHub pull request from a Sentry issue by URL without deleting the ticket or issue; safe to repeat.

Instructions

Remove a linked external ticket or GitHub pull request from a Sentry issue by URL. Deletes only the association, not the ticket or the issue; safe to repeat.

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": {
      "externalIssueUrl": "<externalIssueUrl>"
    },
    "name": "unlink_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
appSlugNoInstalled Sentry App slug. Inferred for Linear and Shortcut URLs; specify it for other Apps.
issueIdNoThe issue short ID, e.g. `PROJECT-1Z43`.
issueUrlNoThe issue URL, e.g. https://my-org.sentry.io/issues/PROJECT-1Z43
regionUrlNo
integrationIdNoNative integration ID, only needed when multiple installations match the URL.
externalIssueUrlYesURL of the existing external ticket or GitHub pull request. For Sentry Apps, the canonical issue URL from the provider.
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
statusYes
issueIdYes
issueUrlYes
externalIssueYes
organizationSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description still adds real value by clarifying the blast radius — only the association is deleted, not the ticket or the Sentry issue — and by restating repeat-safety in human terms.

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 with the action front-loaded and the safety caveat immediately after. Every phrase carries information and nothing is padded.

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 and 86% schema coverage, the description does not need to explain return values or most parameters. It covers the essential semantics for a destructive unlink operation; only explicit alternative-routing guidance is absent.

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 86%, so parameters like externalIssueUrl, appSlug inference, and regionUrl are already well documented. The description only reinforces that the external ticket is identified by URL, adding little beyond the schema; baseline 3 is appropriate.

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 ('Remove a linked external ticket or GitHub pull request from a Sentry issue') and a scoping mechanism ('by URL'). It is the clear inverse of the sibling link_issue, so an agent can distinguish them 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 Guidelines3/5

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

The 'by URL' phrasing implies the operation targets an existing association identified by its URL, and 'safe to repeat' hints at re-invocation tolerance. However, there is no explicit when-to-use vs. when-not guidance or named alternative such as link_issue for the opposite operation.

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