Skip to main content
Glama

Press5 launch pad

Roll back a site

rollback_site
Idempotent

Put an earlier deploy of a site back live. Get deploy ids from site_info.

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": {
      "site": "<site>",
      "deploy": "<deploy>"
    },
    "name": "rollback_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
tokenNoA press5 token (p5_...). Only needed when the MCP connection has no Authorization header, e.g. right after login_check.
deployYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the target is a previously live deploy, but says nothing about what happens to the currently live deploy, whether traffic is interrupted, or what state the site ends in -- context that matters for a rollback.

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 short sentences, the action first and the prerequisite second. Nothing is padded or repeated.

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 and light annotations, the definition covers the essentials for calling the tool but omits the result of the operation and the effect on the current live deploy. Adequate as a minimum viable definition, not rich enough for a state-changing site operation.

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 33%, with only the token parameter documented; 'deploy' is a bare string in the schema. The description usefully clarifies that 'deploy' means an earlier deploy id sourced from site_info, but it leaves the 'site' parameter's expected format (id vs. slug) entirely unexplained.

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 gives a specific verb and resource: putting an earlier deploy of a site back live. That distinguishes it from deploy_site (new deploy) and delete_site without needing another schema, though it never names the sibling it complements.

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 supplies a concrete precondition for use -- obtain the deploy id from site_info first -- which directly enables correct invocation. It stops short of stating when not to use it or how it differs from simply redeploying.

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