Skip to main content
Glama

Promote Revision

promoteRevision
Destructive

Promote a draft or historic revision to the live version. Before calling, confirm with the user which agent and revision will go live and that triggers and new runs will use it. The live revision is the one used by triggers and new runs. Fails if the revision is already live, if a draft revision still has an active builder run, or with 409 if the agent's automation runs as the team and the revision sends cases to a queue that is not in a team automation.

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": {
      "build_id": "<build_id>"
    },
    "name": "promoteRevision"
  }
}

Input Schema

NameRequiredDescriptionDefault
build_idYesThe build's unique identifier
revision_nameNoOptional display name to set on the promoted revision.
revision_descriptionNoOptional description for the promoted revision. Pass null to clear an existing description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the destructiveHint and idempotentHint annotations, the description discloses concrete failure modes: already-live revisions, drafts with active builder runs, and a 409 when the agent runs as the team and the revision targets a queue outside team automation. This is exactly the kind of consequence detail an agent needs before a destructive call.

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 action and its effect come first, followed by the confirmation prerequisite and then failure conditions. The final 409 sentence is dense and clause-heavy but carries real information, so little is wasted.

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 destructive, non-idempotent mutation with no output schema, the description covers the effect on live traffic, the required user confirmation, and the blocking error conditions. Nothing essential to a correct invocation 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?

Schema coverage is 100%, so build_id, revision_name, and revision_description are already documented. The description adds no mapping between those parameters and behavior (e.g., that build_id identifies the revision being promoted), so the baseline of 3 is appropriate.

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 first sentence states a specific verb (promote) and resource (a draft or historic revision) and its effect (becomes the live version). This distinguishes it cleanly from siblings such as promoteSkillRevision and updateRevision.

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 an explicit pre-call requirement: confirm with the user which agent and revision will go live and that triggers and new runs will adopt it. That is clear usage context, though it does not name an alternative tool or a when-not-to-use case.

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