Skip to main content
Glama

Restore a deleted site

restore_site
DestructiveIdempotent

Brings back a site deleted in the last 30 days (list_sites shows them under recently_deleted). It returns offline, with its pages and saved versions; publish_site puts it back online.

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_id": "<site_id>"
    },
    "name": "restore_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site id from list_sites or create_site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the description's added value is the post-condition state: the site comes back offline, with pages and saved versions intact. That is genuinely useful beyond the annotations, but it never explains why the operation is flagged destructive (e.g. name collision or overwrite behavior), leaving an unexplained conflict with the destructiveHint flag.

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 tight sentences: eligibility and discovery first, resulting state and next action second. No filler, no restatement of the title, and the key constraint (30 days) is front-loaded.

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 single-parameter tool with full schema coverage and complete annotations, the description covers eligibility, resulting state, and the follow-up call, which is nearly everything an agent needs. The one remaining hole is the consequence implied by destructiveHint=true — whether restoring can fail on or overwrite an existing site with the same name.

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?

Only one parameter and the schema documents it at 100% coverage ('The site id from list_sites or create_site'). The description adds the pointer that such ids appear under recently_deleted in list_sites, but no format or edge-case guidance for the id itself, 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?

States a specific verb and resource ('Brings back a site') plus the eligibility window (deleted in the last 30 days). It also names the sibling that lists candidates (list_sites) and the sibling that reverses the resulting offline state (publish_site), so an agent can place it in the workflow without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the positive condition (deleted within 30 days) and the discovery path (list_sites shows them under recently_deleted), and names publish_site as the follow-up action to make the site live. The 30-day window functions as the when-not rule, and the alternatives are explicit.

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