Skip to main content
Glama

Get Release

get_release
Read-only

Retrieve full details for a single release, including dates, status, linked issues, hierarchy, and aggregated test run progress across the release and its descendants.

Instructions

Get the full details of one release: dates, status, linked issues, parent/root, and rolled-up progress stats (run counts, test status breakdown across all runs in this release and its descendants). releaseId accepts either the internal _id or a counter-style ID like "MS-12".

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": {
      "projectId": "<projectId>",
      "releaseId": "<releaseId>"
    },
    "name": "get_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesProject ID
releaseIdYesInternal _id or counter-style ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (required)."New value: +"Project ID"
    • changedInput schema / properties / releaseId / description
      Previous value: -"Internal _id or counter-style ID (required)."New value: +"Internal _id or counter-style ID"
  2. Addedv1.0.10

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds meaningful behavior beyond them, notably that the stats are rolled up across all runs in this release AND its descendants, which an agent would not otherwise know. It does not describe failure behavior for an invalid ID.

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, zero filler, with the resource and returned facets front-loaded before the ID-format caveat. The enumeration is long but every listed item corresponds to real returned data.

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?

With no output schema, the description carries the burden of explaining return values and does so adequately, including the descendant-rollup semantics of the stats. Remaining gaps, such as not-found behavior, are minor for a read-only single-entity fetch.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3. The description goes beyond the schema by giving a concrete counter-style example ('MS-12') for releaseId, which clarifies the accepted ID format in a way the terse schema text does not.

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 gives a specific verb and resource ('Get the full details of one release') and enumerates the returned facets: dates, status, linked issues, parent/root, and rolled-up stats. It does not explicitly contrast itself with siblings such as get_project_details or update_release, so it falls short of a 5, but the singular-release scope is unambiguous.

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?

Use is only implied: an agent can infer this is the lookup for a single known release, versus create_release or update_release. There is no explicit when-to-use statement, no mention of what to do when the release is unknown, and no named alternative for listing releases.

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