Skip to main content
Glama

List a project's releases

r3_release_list
Read-only

List the releases of an R3 project, newest first: number, date, who made it, note, size, which one is LIVE (what the public URL shows), pinned, and releases in the trash (restorable for 7 days). Also says whether the project has saved changes that are not live yet: saving does NOT change the live site; r3_publish_live does. Read-only. Needs the project:read right.

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>"
    },
    "name": "r3_release_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe project id (r3_project_list).

Output Schema

NameRequiredDescriptionDefault
liveYes
answerYesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.
releasesYes
projectIdYes
changesNotLiveYes
liveReleaseNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / releases / items / properties / modules
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "version": {
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "version"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / releases / items / required
      Previous value: -[
      -  "number",
      -  "createdAt",
      -  "createdByName",
      -  "via",
      -  "agentLabel",
      -  "note",
      -  "sizeBytes",
      -  "componentCount",
      -  "live",
      -  "pinned",
      -  "incomplete",
      -  "trashed"
      -]New value: +[
      +  "number",
      +  "createdAt",
      +  "createdByName",
      +  "via",
      +  "agentLabel",
      +  "note",
      +  "sizeBytes",
      +  "componentCount",
      +  "modules",
      +  "live",
      +  "pinned",
      +  "incomplete",
      +  "trashed"
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / answer
      Added value: +{
      +  "description": "This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "projectId",
      -  "live",
      -  "liveReleaseNumber",
      -  "changesNotLive",
      -  "releases"
      -]New value: +[
      +  "projectId",
      +  "live",
      +  "liveReleaseNumber",
      +  "changesNotLive",
      +  "releases",
      +  "answer"
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only' is largely redundant. The description still earns credit by adding the required 'project:read' right, newest-first ordering, and the 7-day restorability window for trashed releases — behavioral facts absent from the annotations.

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?

The ordering and return contents are front-loaded in the first sentence, with behavioral notes (save vs. publish, read-only, permission) following. It is dense but every clause carries information, though the enumerated return fields sit close to redundancy given an output schema exists.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with annotations and an output schema, the description covers ordering, permission requirement, trash retention, and the crucial save-vs-publish distinction. An agent has everything needed to call it correctly and interpret the LIVE marker.

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 at 100% schema coverage, and the schema already tells the agent to obtain the id from r3_project_list. The description adds no syntactic or formatting guidance for projectId, so the baseline of 3 applies.

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?

The description states a specific verb and resource ('List the releases of an R3 project') and further enumerates exactly what each entry contains (number, date, author, note, size, LIVE marker, pinned, trashed). The 'LIVE (what the public URL shows)' gloss distinguishes this listing from publish-related siblings like r3_publish_live and r3_release_rollback.

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?

It gives real contextual routing: saving does NOT change the live site, whereas r3_publish_live does, and it notes the listing reports pending non-live changes. It does not explicitly say when to prefer this over r3_project_changes or when to follow with r3_release_restore/r3_release_rollback, so it stops short of full alternative coverage.

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