Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Find Releases

find_releases
Read-only

List or search Sentry releases by organization or project to inspect version deployment dates, new issue counts, last commits, and last deploys.

Instructions

List or search releases (deployed versions) in a Sentry organization or project. Returns each release's dates, new issue count, last commit, and last deploy. Returns at most 25 releases with no next page; narrow by project or version to see others.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
queryNo
regionUrlNo
projectSlugNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
hasMoreYes
releasesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, open-world behavior, so the description's main value-add is the hard cap: 'at most 25 releases with no next page'. That is a real behavioral constraint an agent must plan around and is not derivable from structured fields. It does not disclose ordering/sort semantics or whether the cap is per-project or per-org, which keeps it from a 5.

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?

Three sentences, zero filler. The purpose, the returned fields, and the pagination limitation are each front-loaded in a logical order, with the most decision-relevant constraint (25-releases cap, no next page) placed last for emphasis.

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 the brief return-field summary is a convenience rather than a necessity, and the 25-item cap fills the biggest operational gap. Remaining gaps, such as sort order and empty-result behavior, are minor for a read-only listing tool with full annotation coverage.

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 only 40%, so the description bears more weight than usual; it does explain that results can be narrowed by 'project or version', mapping to projectSlug and query. However, fresh, regionUrl, and organizationSlug are not elaborated in the description, and no format or syntax detail (e.g. what the version substring matches against) is added beyond the schema.

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+resource, 'List or search releases', and disambiguates the resource with the parenthetical '(deployed versions)'. The scope, 'in a Sentry organization or project', plus the mention of project/version narrowing, makes it distinguishable from the other find_* lookup siblings without opening a schema.

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

Usage Guidelines3/5

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

Offers operational guidance, 'narrow by project or version to see others', which tells the agent how to work around the result cap. It stops short of stating when to reach for this versus related tools such as find_projects or find_organizations, or any prerequisite for the organization/region context, so usage is implied rather than spelled out.

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