Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Release Details

get_release_details
Read-only

Retrieves a Sentry release by exact version, including its projects, deploys, environments, recent commits, and optional release health.

Instructions

Get one Sentry release by exact version: its projects, deploys, environments, recent commits, and optionally release health (adoption stages and session bounds). To find issues introduced in a release, use search_issues with release:<version>.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "releaseVersion": "<releaseVersion>"
    },
    "name": "get_release_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
limitNoMaximum deploys and commits to return, each.
regionUrlNo
includeHealthNoInclude release health for one project. Requires projectSlugOrId unless the session is limited to a project.
includeCommitsNoInclude recent commits.
includeDeploysNoInclude recent deploys.
releaseVersionYesExact release version.
projectSlugOrIdNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
healthYesRelease health metadata. Null unless includeHealth is true.
commitsYesRecent commits. Null when includeCommits is false.
deploysYesRecent deploys. Null when includeDeploys is false.
releaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds useful content scope by naming the returned sub-resources and flagging release health as opt-in with 'adoption stages and session bounds'. It does not mention that `fresh` bypasses caching or any rate-limit/latency behavior, which would be the remaining value-add for an open-world read.

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?

Two sentences, front-loaded with the identity of the resource and its payload, then the disambiguation. Nothing is repeated and no sentence is padding.

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

Completeness4/5

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

An output schema exists, so return-value explanation is unnecessary, and the description covers purpose, contents, and the adjacent-tool boundary for a 9-parameter read tool. The minor gap is that it says nothing about the organization/region context required to address the release, which is left entirely to the schema.

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 78%, close to the high-coverage baseline, and the schema already documents `limit`, `fresh`, `regionUrl`, `includeHealth`'s project dependency, and `releaseVersion`. The description reinforces 'exact version' and explains what health data actually contains, but adds no syntax, format, or default behavior beyond the schema, so baseline 3 fits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get one Sentry release by exact version') and enumerates the payload: projects, deploys, environments, recent commits, optional health. The exact-version constraint also implicitly separates it from any fuzzy/list-style release lookup, so an agent knows what input shape is required.

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

Usage Guidelines4/5

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

Explicitly routes issue-related questions away to search_issues with `release:<version>`, which is a real, named alternative with a condition. It stops short of the full picture: it doesn't say what to do when the exact version string is unknown (e.g., no release-listing alternative is referenced), so guidance is clear but not exhaustive.

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