Skip to main content
Glama

Restore a site version

restore_version
Destructive

Restores a previous version of a site (version_id from list_versions) and publishes it. The current version is saved to history first, so this can be undone.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id or name, e.g. "my-portfolio" or "my-portfolio.hostilo.page" (from list_sites).
version_idYesversion_id from list_versions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / site / description
      Previous value: -"Site id or name, e.g. \"my-portfolio\" or \"my-portfolio.hostilo.app\" (from list_sites)."New value: +"Site id or name, e.g. \"my-portfolio\" or \"my-portfolio.hostilo.page\" (from list_sites)."
  2. 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 destructiveHint=true and idempotentHint=false, so the description's real contribution is disclosing the two-step behavior: the restored version is published, and the current version is snapshotted to history first, making the operation reversible. That undo path meaningfully softens the destructive hint. It does not mention permission requirements or the fact that publishing exposes the site publicly (openWorldHint=true), which would have completed the picture.

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, zero filler, with the primary action and its publish side effect front-loaded and the safety-relevant history behavior second. Every clause carries information an agent needs.

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?

For a two-parameter mutation with full schema coverage, no output schema, and annotations covering the safety profile, the description supplies what structured fields cannot: the publish side effect and the automatic backup. Only minor gaps remain, such as auth requirements and whether the restore is immediately live.

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 both parameters are already documented, including the site id/name format and the origin of version_id. The description reinforces that version_id comes from list_versions but adds no new syntax, constraints, or format detail beyond the schema. Baseline 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?

States a specific verb and resource ('Restores a previous version of a site') and immediately adds the secondary effect ('publishes it'), which distinguishes it from update_site and publish_files. It also names the sibling that supplies the version_id, so an agent can identify the tool's role without opening the schema.

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?

The parenthetical '(version_id from list_versions)' gives explicit routing guidance for obtaining the required input, which is the main prerequisite. There is no explicit when-not-to-use guidance versus update_site or publish_files, but the restore-and-publish semantics make the boundary reasonably inferable.

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.