Skip to main content
Glama

List releases

list_releases
Read-onlyIdempotent

Read cached releases and store review/rollout states, with the app’s last store sync. A row’s pulledAt is when the store last confirmed it; syncedAt is the last synchronization of the whole app. Success of an operation does not mean the release is live.

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

Input Schema

NameRequiredDescriptionDefault
appIdYes
cursorNo
includeArchivedNoInclude archived placeholders and expired TestFlight builds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / includeArchived
      Added value: +{
      +  "default": false,
      +  "description": "Include archived placeholders and expired TestFlight builds.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, and the description adds real behavioral context: that data is cached, the pulledAt vs syncedAt distinction, and the caveat that success is not liveness. It stops short of describing pagination or result shape.

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?

Three tight sentences, front-loaded with the core action, with the field definitions kept short. The second sentence is somewhat dense but each clause carries information an agent needs to interpret results.

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

Completeness3/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 usefully explains pulledAt/syncedAt and the liveness caveat. However, it leaves cursor pagination and includeArchived behavior unaddressed and provides no guidance on the untyped appId, so it is only partially complete for a 3-parameter tool.

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

Parameters2/5

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

Schema coverage is only 33%: includeArchived is documented in the schema, but appId and cursor are not. The description never explains the appId scope or cursor-based pagination; its pulledAt/syncedAt explanation addresses return fields, not parameters, so it doesn't compensate for the coverage gap.

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?

States a specific verb and resource: 'Read cached releases and store review/rollout states, with the app's last store sync.' The word 'cached' meaningfully separates it from live-check siblings like check_apple_release, though it never names that sibling directly.

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 is only implied: 'cached' plus 'Success of an operation does not mean the release is live' hints that a live check belongs elsewhere, but no alternative tool or when-not-to-use condition is stated. The agent must infer the routing from sibling names.

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