Skip to main content
Glama

project_restore_version

Idempotent

Restore a specific past deploy version to be the live production version. Restoring by number leaves the database schema and data unchanged. project_deploys shows which versions are available: an entry with rollback_available: false is still in the history but its build is no longer restorable (the call is refused and nothing changes — deploying that version's source again brings it back). The currently live version is a no-op. Free can restore a retained deploy from the last 24 hours or roll back to the previous working version. Paid plans can restore any retained version.

Example:

{ "project_id": "my-saas", "version": 11 }

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": {
      "project_id": "<project_id>",
      "version": "<version>"
    },
    "name": "project_restore_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesVersion number to restore (from project_deploys)
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations it discloses the key behavioral fact an agent needs: restoring by number leaves the database schema and data unchanged, i.e. it is not a data-destructive operation. It also explains the refusal path for unbuildable versions (and that redeploying the source revives it), the no-op on the live version, and plan-tier limits. This is materially more than readOnlyHint=false / idempotentHint=true / destructiveHint=false conveys.

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 core action and its safety profile are front-loaded in the first two sentences, followed by discovery, failure mode, and entitlement rules. It is dense but nearly every sentence carries operational information; the plan-entitlement sentence is the longest and is only partly needed to decide the call.

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 two-parameter mutation with annotations and no output schema, the description covers action, safety, discovery of valid inputs, refusal behavior, no-op behavior, and entitlement gating. An agent has enough to decide whether to call it and to predict the outcome.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are already documented, including that version numbers come from project_deploys. The description reinforces that linkage and provides a concrete call example showing both fields together, which clarifies relative sizing and format slightly beyond the schema.

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 first sentence names a specific verb and resource with scope: restore a past deploy version to be the live production version. It also points at project_deploys as the source of valid version numbers. It does not distinguish itself from the sibling project_rollback, which sounds closely related, so an agent must guess between the two.

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 concrete when-not conditions: restoring the currently live version is a no-op, and a version with rollback_available:false is refused with nothing changed. Plan-based eligibility (Free = 24h retention or previous working version; Paid = any retained version) further constrains when the call can succeed. The one gap is that it never routes the agent to project_rollback as an alternative.

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