Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Add Issue Note

add_issue_note

Posts a comment to a Sentry issue's activity feed so the whole team can see findings or decisions. Use it to document investigation notes—never include secrets or credentials.

Instructions

Add a comment (note) to a Sentry issue's activity feed, visible to the whole team. Use it to record findings or decisions; never post secrets or credentials.

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": {
      "text": "<text>"
    },
    "name": "add_issue_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe comment text, posted as is.
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
noteYes
issueIdYes
issueUrlYes
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 readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is known. The description adds genuinely new context: the note is visible to the whole team, which matters for an externally-facing write, plus an explicit data-safety constraint. It does not say whether notes can later be edited or removed, but that is secondary.

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 short sentences, front-loaded with what the tool does and what the result means for visibility, followed by a single usage directive. No filler or repetition of the schema.

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 exists and annotations cover the safety profile, so the description only needs to supply mutation context — which it does via team visibility and the secrets warning. For a five-parameter tool with one required field, the remaining gap (no note about whether posting is idempotent or editable) is minor.

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 80%, so the schema already documents all five parameters, including the issueId vs. issueUrl alternatives and the regionUrl hint pointing to find_organizations. The description adds no parameter-level meaning beyond the schema, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Add a comment (note) to a Sentry issue's activity feed') and clarifies that a note is the same object as a comment. It is clearly distinguishable from read-side siblings like get_issue_activity, but it never names or contrasts an alternative explicitly.

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?

It gives an affirmative use case ('record findings or decisions') and a prohibition ('never post secrets or credentials'), so the agent knows the intended context. It stops short of stating when to prefer another tool (e.g., update_issue for changing issue state), leaving routing to inference.

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