Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

sentry_list_releases

Retrieve and display release information for a Sentry project to monitor deployment versions and track application changes.

Instructions

List releases for a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectSlugYesProject slug/identifier

Implementation Reference

  • MCP tool handler for sentry_list_releases: extracts projectSlug from args, calls apiClient.listReleases, and formats response with top 10 releases.
    case "sentry_list_releases": {
      if (!apiClient) {
        throw new Error("Sentry API client not initialized. Provide auth token.");
      }
      
      const { projectSlug } = args as any;
      const releases = await apiClient.listReleases(projectSlug);
      
      return {
        content: [
          {
            type: "text",
            text: `Found ${releases.length} releases:\n${releases.slice(0, 10).map((r: any) => 
              `- ${r.version} (${new Date(r.dateCreated).toLocaleDateString()})`
            ).join('\n')}${releases.length > 10 ? '\n... and more' : ''}`,
          },
        ],
      };
    }
  • src/index.ts:442-455 (registration)
    Tool registration in ListToolsRequestSchema response, including name, description, and input schema requiring projectSlug.
    {
      name: "sentry_list_releases",
      description: "List releases for a project",
      inputSchema: {
        type: "object",
        properties: {
          projectSlug: {
            type: "string",
            description: "Project slug/identifier",
          },
        },
        required: ["projectSlug"],
      },
    },
  • Input schema for sentry_list_releases tool: requires projectSlug string.
    inputSchema: {
      type: "object",
      properties: {
        projectSlug: {
          type: "string",
          description: "Project slug/identifier",
        },
      },
      required: ["projectSlug"],
    },
  • Core API helper method in SentryAPIClient that performs HTTP request to fetch releases for a project.
    async listReleases(projectSlug: string) {
      return this.request(`/projects/${this.org}/${projectSlug}/releases/`);
    }
  • Private request method used by all API calls, including listReleases, handling auth and error checking.
    private async request(endpoint: string, options: any = {}) {
      const url = `${this.baseUrl}${endpoint}`;
      const response = await fetch(url, {
        ...options,
        headers: {
          'Authorization': `Bearer ${this.authToken}`,
          'Content-Type': 'application/json',
          ...options.headers,
        },
      });
    
      if (!response.ok) {
        throw new Error(`Sentry API error: ${response.status} ${response.statusText}`);
      }
    
      return response.json();
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It doesn't disclose behavioral traits such as whether this is a read-only operation (implied by 'List' but not explicit), pagination behavior, rate limits, authentication needs, or what the output format looks like. For a list operation with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action ('List releases') and appropriately sized for a simple tool, making it easy to parse quickly.

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 tool's simplicity (one parameter, no output schema, no annotations), the description is incomplete. It lacks information on output format, pagination, error handling, or behavioral context. For a list tool in a sibling-rich environment, more completeness is needed to help an agent use it effectively without guesswork.

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?

The description adds minimal meaning beyond the input schema, which has 100% coverage for the single parameter 'projectSlug'. The description implies the parameter is needed ('for a project') but doesn't provide additional context like format examples or how to obtain the slug. With high schema coverage, the baseline is 3, and the description doesn't significantly enhance parameter understanding.

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 'List releases for a project' clearly states the verb ('List') and resource ('releases'), with the scope ('for a project') implied by the required parameter. It distinguishes from siblings like 'sentry_create_release' (create vs. list) and 'sentry_list_projects' (projects vs. releases), but doesn't explicitly differentiate from 'sentry_list_issues' or 'sentry_list_error_events_in_project' in terms of what type of data is listed.

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing project), exclusions, or compare to siblings like 'sentry_list_issues' for different data types. The description only states what it does, not when it's appropriate.

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