Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Link Issue

link_issue
Idempotent

Links an existing external ticket or GitHub pull request to a Sentry issue by URL, adding a reference without creating the ticket or changing issue status.

Instructions

Link an existing external ticket or GitHub pull request to a Sentry issue by URL: Jira, GitHub, GitLab, Bitbucket, Azure DevOps, or an installed Sentry App such as Linear. Adds a reference only; it does not create the ticket or change the issue status (use update_issue).

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoExtra form values by field name, for a Sentry App that requires them.
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.4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description reinforces the limited mutation scope by saying only a reference is added. It does not cover permission requirements or what happens when the same URL is linked twice, but the annotation set carries those semantics.

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 with no filler. The purpose and provider list come first and the scope constraint plus alternative follow immediately.

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?

An output schema and rich annotations exist, and the description covers purpose, scope limits, and the status-change alternative. Minor gaps remain around organization/region parameters and URL-matching failure modes, but those are documented in the schema.

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 88%, so the schema already explains most parameters including appSlug inference for Linear and Shortcut. The description adds value by naming the concrete provider set that externalIssueUrl accepts, which the schema only gestures at generically.

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 ("Link an existing external ticket or GitHub pull request to a Sentry issue by URL") and enumerates the supported providers. It also explicitly separates itself from update_issue by noting it does not change issue status.

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?

Provides a clear when-not ("Adds a reference only; it does not create the ticket or change the issue status") and routes status changes to update_issue. It stops short of naming unlink_issue as the reversal path or stating prerequisites, so the alternative coverage is not exhaustive.

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