Skip to main content
Glama

list_builds

Read-only

List an app's uploaded builds newest first, including version, platform, build type, upload time, note, and retention status. Use a debug build id with dev_start to launch a session.

Instructions

List an app's uploaded builds, newest first: id, version, build number, platform, kind (debug/release/unknown), upload time, note and retention (keep, expires_on as YYYY-MM-DD, expired; absent on older servers). Pass a debug build's id to dev_start as build_id.

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": {
      "app": "<app>"
    },
    "name": "list_builds"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesApp id (from list_apps or upload_app).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real behavior beyond that: the sort order, the full returned field set, the debug/release/unknown kind enum, and the retention states including that the field is absent on older servers. Pagination or result limits for large build lists are not mentioned.

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 tight sentences, front-loaded with purpose and ordering, followed by the field list and then the cross-tool hint — no filler clauses.

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 usefully enumerates the return shape and its edge cases, which is exactly what an agent needs to use the result. Only a note on result size or paging is missing.

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?

Single parameter with 100% schema description coverage that already explains where the app id comes from (list_apps or upload_app), so the baseline is 3. The description adds no further guidance on the app value.

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 ('List an app's uploaded builds') with an explicit ordering ('newest first') and enumerates the returned fields, so it is clearly distinguishable from list_apps.

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?

Gives a concrete downstream handoff ('Pass a debug build's id to dev_start as build_id'), which tells the agent what to do after calling it. It does not spell out exclusions or when-not-to-use, but there is no close sibling list_builds alternative among the tools.

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