Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

sentry_list_error_events_in_project

List recent error events from a Sentry project to monitor frequency patterns and occurrence timestamps for debugging.

Instructions

List error events from a specific Sentry project. View recent errors, frequency patterns and occurrence timestamps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectSlugYesProject slug/identifier
limitNoNumber of events to return
queryNoSearch query

Implementation Reference

  • MCP tool handler that extracts parameters, calls SentryAPIClient.listErrorEventsInProject, and formats the response as text content listing error events.
    case "sentry_list_error_events_in_project": {
      if (!apiClient) {
        throw new Error("Sentry API client not initialized. Provide auth token.");
      }
      
      const { projectSlug, limit = 50, query } = args as any;
      const events = await apiClient.listErrorEventsInProject(projectSlug, { limit, query });
      
      return {
        content: [
          {
            type: "text",
            text: `Found ${events.length} error events in project ${projectSlug}:\n` +
              events.map((e: any) => `- ${e.title} (${e.eventID}) - ${e.dateCreated}`).join('\n'),
          },
        ],
      };
    }
  • Tool schema definition including name, description, and input schema with projectSlug required, optional limit and query.
      name: "sentry_list_error_events_in_project",
      description: "List error events from a specific Sentry project. View recent errors, frequency patterns and occurrence timestamps.",
      inputSchema: {
        type: "object",
        properties: {
          projectSlug: {
            type: "string",
            description: "Project slug/identifier",
          },
          limit: {
            type: "number",
            description: "Number of events to return",
            default: 50,
          },
          query: {
            type: "string",
            description: "Search query",
          },
        },
        required: ["projectSlug"],
      },
    },
  • Core implementation in SentryAPIClient that constructs and sends HTTP request to Sentry API endpoint for project events using the provided parameters.
    async listErrorEventsInProject(projectSlug: string, params?: any) {
      const queryParams = params ? '?' + new URLSearchParams(params).toString() : '';
      return this.request(`/projects/${this.org}/${projectSlug}/events/${queryParams}`);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions listing error events but fails to specify if this is a read-only operation, whether it requires specific permissions, if there are rate limits, or what the output format looks like. The phrase 'View recent errors' implies a read operation, but lacks details on pagination, sorting, or error handling.

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 concise with two sentences that are front-loaded with the main purpose. The second sentence adds some context but could be more tightly integrated. There's no wasted text, though it could be slightly more structured for clarity.

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 the complexity of listing error events, no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, rate limits, or output format, and lacks usage guidelines. For a tool with 3 parameters and no structured safety hints, more context is needed to be fully helpful.

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 all parameters (projectSlug, limit, query). The description adds no additional meaning beyond what's in the schema, such as explaining how the query parameter works or what 'recent' means in context. Baseline 3 is appropriate when the schema handles parameter documentation adequately.

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 'error events from a specific Sentry project', making the purpose understandable. It distinguishes from siblings like sentry_list_issues or sentry_list_issue_events by specifying 'error events' rather than issues or other event types. However, it doesn't explicitly contrast with sentry_search_errors_in_file, which might be a close alternative.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions 'View recent errors, frequency patterns and occurrence timestamps' but doesn't specify if this is for monitoring, debugging, or other contexts, nor does it reference sibling tools like sentry_list_issues or sentry_search_errors_in_file for comparison.

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