selfhosted-sentry-mcp

list_activity

Read-onlyIdempotent

Retrieve an issue's activity log to review comments, assignments, status changes, and other events for troubleshooting or audit.

Instructions

List activity log for an issue. Shows comments, assignments, status changes, and other events.

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>"
    },
    "name": "list_activity"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max activities (1-100, default: 25).
`cursor`	No	Pagination cursor.
`issue_id`	Yes	Numeric issue ID or short ID (e.g. PROJ-1A2).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026
- changedInput schema / properties / issue_id / description
```
Previous value: -"Issue ID."New value: +"Numeric issue ID or short ID (e.g. PROJ-1A2)."
```
First observedv1.2.0Jul 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful context by enumerating which event types appear in the log, but says nothing about pagination behavior, ordering, or result size despite exposing a cursor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler; the purpose is front-loaded and the second sentence earns its place by listing the returned event categories. Slightly redundant with the resource name in the title, but tight overall.

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?

For a read-only, three-parameter list tool with full schema coverage and rich annotations but no output schema, the description gives enough to call it correctly. The only mild gap is not clarifying its relationship to the other event-listing siblings.

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 100%, so the schema already documents limit, cursor, and issue_id formats (including the PROJ-1A2 example). The description adds no parameter-level detail beyond that, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb and resource ('List activity log for an issue') and enumerates the content returned (comments, assignments, status changes). It is clear, but it does not explicitly distinguish itself from overlapping siblings such as list_issue_events or list_breadcrumbs, which also return per-issue event data.

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 use it (fetching an issue's activity trail), but there is no explicit when-to-use, no exclusions, and no pointer to alternatives like list_issue_events or list_breadcrumbs. Usage is inferable rather than stated.

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