Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Issue Activity

get_issue_activity
Read-only

Retrieve a Sentry issue's activity feed and comments to identify who resolved, ignored, assigned, or commented on it and when.

Instructions

Get the activity feed and comments of a Sentry issue: who resolved, ignored, assigned, or commented on it, and when.

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

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
limitNo
issueIdNoThe issue short ID, e.g. `PROJECT-1Z43`.
issueUrlNoThe issue URL, e.g. https://my-org.sentry.io/issues/PROJECT-1Z43
regionUrlNo
includeCommentsNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
issueIdYes
activityYes
commentsYesNull when includeComments is false.
issueUrlYes
organizationSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.3/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. The description adds no behavior beyond that: it says nothing about caching and the fresh bypass, result limits, ordering, or how comments are merged into the feed. It does at least imply the read is a historical audit view, which is modest added context.

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?

One sentence, front-loaded with the verb and resource, then the payload detail. Every clause earns its place and nothing is padded.

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

Completeness3/5

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

An output schema exists, so return-shape explanation isn't required, and the annotations cover safety. Still, for a seven-parameter tool with partial schema coverage, the description leaves key call-shaping questions (identifier choice, region routing, cache bypass, limits) unanswered.

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

Parameters2/5

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

Schema coverage is only 57% and the description explains none of the seven parameters. It doesn't clarify that issueId is a short ID versus issueUrl, how organizationSlug/regionUrl gate the call, that includeComments defaults to true, or that fresh bypasses cache. The mention of comments gestures at includeComments but never states the toggle.

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?

It names a specific verb and resource (activity feed and comments of a Sentry issue) and enumerates the activity kinds it surfaces (resolved, ignored, assigned, commented). That distinguishes it from get_issue_details and get_issue_breadcrumbs without naming them explicitly.

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 scope implies when to reach for it (you want the human audit trail on an issue), but there is no explicit guidance on when to prefer get_issue_details, get_issue_breadcrumbs, or search_issue_events instead, and no stated prerequisites.

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