Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

sentry_list_issue_events

Retrieve and analyze events for a specific Sentry issue to examine details, metadata, and identify patterns in application errors.

Instructions

List events for a specific Sentry issue. Analyze event details, metadata and patterns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdYesIssue ID
limitNoNumber of events to return

Implementation Reference

  • MCP tool handler that extracts parameters, calls apiClient.listIssueEvents(issueId), slices to limit, and formats a text response listing the events.
    case "sentry_list_issue_events": {
      if (!apiClient) {
        throw new Error("Sentry API client not initialized. Provide auth token.");
      }
      
      const { issueId, limit = 50 } = args as any;
      const events = await apiClient.listIssueEvents(issueId);
      
      return {
        content: [
          {
            type: "text",
            text: `Found ${events.length} events for issue ${issueId}:\n` +
              events.slice(0, limit).map((e: any) => 
                `- ${e.eventID} - ${e.dateCreated} - ${e.message || e.title}`
              ).join('\n'),
          },
        ],
      };
    }
  • Input schema definition for the tool, specifying issueId as required string and optional limit number.
    {
      name: "sentry_list_issue_events",
      description: "List events for a specific Sentry issue. Analyze event details, metadata and patterns.",
      inputSchema: {
        type: "object",
        properties: {
          issueId: {
            type: "string",
            description: "Issue ID",
          },
          limit: {
            type: "number",
            description: "Number of events to return",
            default: 50,
          },
        },
        required: ["issueId"],
      },
  • src/index.ts:596-613 (registration)
    Tool registration in the ListToolsRequestSchema handler's tools array.
    {
      name: "sentry_list_issue_events",
      description: "List events for a specific Sentry issue. Analyze event details, metadata and patterns.",
      inputSchema: {
        type: "object",
        properties: {
          issueId: {
            type: "string",
            description: "Issue ID",
          },
          limit: {
            type: "number",
            description: "Number of events to return",
            default: 50,
          },
        },
        required: ["issueId"],
      },
  • Core API client method that performs the HTTP request to Sentry API endpoint /issues/{issueId}/events/ to fetch the list of events.
    async listIssueEvents(issueId: string) {
      return this.request(`/issues/${issueId}/events/`);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions analyzing event details, metadata, and patterns, but fails to disclose critical behavioral traits such as pagination, rate limits, authentication needs, or what 'analyze' entails operationally. This leaves significant gaps for an agent.

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?

The description is brief and front-loaded with the core purpose, but the second sentence ('Analyze event details, metadata and patterns') is vague and doesn't add clear operational value, slightly reducing efficiency.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It lacks details on return values, error handling, or behavioral context needed for a tool with two parameters and sibling alternatives, making it inadequate for full agent understanding.

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 both parameters (issueId and limit). The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, resulting in a baseline score of 3.

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 clearly states the verb 'List' and resource 'events for a specific Sentry issue', making the purpose understandable. It distinguishes from siblings like 'sentry_list_issues' by focusing on events per issue, but could be more explicit about the difference from 'sentry_list_error_events_in_project'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like 'sentry_list_error_events_in_project' or 'sentry_get_event'. The description implies usage for analyzing event details, but lacks context on prerequisites, timing, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/diegofornalha/sentry-mcp-cursor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server