Skip to main content
Glama
HieuAnh87

selfhosted-sentry-mcp

by HieuAnh87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_sentry_issues

Read-onlyIdempotent

List issues for a Sentry project by slug, with optional query or status filters and pagination, to triage errors and monitor unresolved work.

Instructions

List issues for a specific project, optionally filtering by query or status. Supports pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoReturn Sentry's full issue objects (stats, annotations, flags) instead of the compact triage fields (default: false).
limitNoMax issues (1-100, default: 25).
queryNoOptional Sentry search query.
cursorNoPagination cursor (next_cursor from a previous call).
statusNoFilter by status.
project_slugYesThe slug of the project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor."New value: +"Pagination cursor (next_cursor from a previous call)."
    • addedInput schema / properties / full
      Added value: +{
+  "description": "Return Sentry's full issue objects (stats, annotations, flags) instead of the compact triage fields (default: false).",
+  "type": "boolean"
+}
  2. First observedv1.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds that pagination is supported, but doesn't explain return shape or the full vs compact tradeoff (left to the schema).

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, front-loaded with the core action and scoping, with minimal waste. Slightly terse given the ambiguity with a sibling tool, but efficient.

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?

The schema is fully described and annotations cover the safety profile, so the mechanical calling information is complete. However, the overlap with sibling list_issues is unaddressed, leaving a meaningful selection gap for the agent.

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 coverage is 100%, so all six parameters are already documented in the schema; the description only echoes query/status and pagination. Baseline 3 is appropriate 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?

The description states a clear verb (list) and resource (issues) scoped to a specific project, with optional filtering. It does not, however, distinguish itself from the sibling tool list_issues, which an agent could easily confuse it with.

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?

It mentions that filtering by query or status is optional and that pagination is supported, which implies usage, but gives no guidance on when to prefer this over list_issues or other siblings, and no exclusions or prerequisites.

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

Deploy Server

Other Tools