Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

sentry_create_release

Create new releases in Sentry with version details, project associations, URLs, and release dates to track application deployments and monitor error occurrences.

Instructions

Create a new release

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionYesRelease version (e.g., 'myapp@1.0.0')
projectsNoList of project slugs
urlNoRelease URL
dateReleasedNoRelease date (ISO format)

Implementation Reference

  • The tool handler that processes the CallToolRequest for sentry_create_release, extracts parameters, checks for apiClient, calls apiClient.createRelease, and returns success message.
    case "sentry_create_release": {
      if (!apiClient) {
        throw new Error("Sentry API client not initialized. Provide auth token.");
      }
      
      const { version, projects, url, dateReleased } = args as any;
      const release = await apiClient.createRelease(version, {
        projects,
        url,
        dateReleased: dateReleased || new Date().toISOString(),
      });
      
      return {
        content: [
          {
            type: "text",
            text: `Release created: ${release.version}\nProjects: ${release.projects?.join(', ') || 'none'}`,
          },
        ],
      };
    }
  • Tool schema definition including name, description, and inputSchema for sentry_create_release.
    {
      name: "sentry_create_release",
      description: "Create a new release",
      inputSchema: {
        type: "object",
        properties: {
          version: {
            type: "string",
            description: "Release version (e.g., 'myapp@1.0.0')",
          },
          projects: {
            type: "array",
            items: { type: "string" },
            description: "List of project slugs",
          },
          url: {
            type: "string",
            description: "Release URL",
          },
          dateReleased: {
            type: "string",
            description: "Release date (ISO format)",
          },
        },
        required: ["version"],
      },
    },
  • The createRelease method in SentryAPIClient that makes the POST request to Sentry API to create the release using the private request method.
    async createRelease(version: string, data: any = {}) {
      return this.request(`/organizations/${this.org}/releases/`, {
        method: 'POST',
        body: JSON.stringify({
          version,
          ...data,
        }),
      });
    }
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 for behavioral disclosure. 'Create a new release' implies a write operation, but it doesn't disclose permissions needed, whether it's idempotent, rate limits, error conditions, or what happens on success (e.g., returns a release ID). For a mutation tool 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 wasted words. It's front-loaded with the core action ('Create a new release'), making it immediately scannable. Every word earns its place by conveying the essential purpose without redundancy.

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 this is a mutation tool (creating a release) with no annotations and no output schema, the description is incomplete. It doesn't explain what a 'release' means in Sentry context, what happens after creation, or any behavioral aspects. The agent lacks context about success responses, error handling, or system impact, making it inadequate for safe invocation.

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 fully documents all 4 parameters (version, projects, url, dateReleased) with descriptions. The description adds no parameter information beyond what's in the schema. According to guidelines, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description.

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 'Create a new release' clearly states the verb ('create') and resource ('release'), making the purpose immediately understandable. It distinguishes from sibling tools like 'sentry_list_releases' (which lists) and 'sentry_set_release' (which sets), though it doesn't explicitly differentiate from 'sentry_create_project' or 'sentry_create_alert_rule' beyond the resource type.

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 doesn't mention prerequisites (e.g., needing an existing project), when not to use it (e.g., for updating releases), or how it relates to sibling tools like 'sentry_list_releases' or 'sentry_set_release'. The agent must infer usage from the name alone.

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