Skip to main content
Glama

List releases

list_releases
Read-onlyIdempotent

Lists retained, completely published releases and the active release pointer for an exact authorized project.

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": {
      "project_id": "<project_id>"
    },
    "name": "list_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesExact stable project ID. Resolve it first. Never invent an update target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description's burden is lighter. It still adds real value by disclosing the result shape and filtering rule: only retained, fully published releases are returned, alongside the active release pointer, which tells the agent that draft/incomplete releases are silently excluded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with no filler, and the key scoping information (retained, published, active pointer) is front-loaded. It could be marginally improved by separating the return-content clause from the prerequisite clause for faster scanning.

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?

This is a low-complexity read tool with one fully documented parameter and complete annotations, and there is no output schema. The description covers both what is queried and roughly what comes back (releases plus active pointer), leaving only pagination/ordering unspecified, which is a minor gap.

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?

There is a single parameter with 100% schema description coverage, including an ID pattern and the instruction to resolve the ID first. The description reinforces this with "exact authorized project" but adds no format, syntax, or edge-case detail beyond what the schema already states, so the baseline 3 applies.

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 pairs a specific verb ("Lists") with a specific resource ("releases") and narrows scope with three qualifiers: retained, completely published, and the active release pointer. This clearly separates it from mutation siblings like activate_release or rollback_project, though it never names an alternative explicitly.

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?

Usage context is only implied: "for an exact authorized project" signals a prerequisite (authorization and a resolved project ID) but does not state when to call this versus activating or rolling back a release. An agent must infer that this is the read/discovery step before a release mutation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources