Skip to main content
Glama

Pagetool

Archive an unpublished site

archive_site
Destructive

Removes one of your own UNPUBLISHED sites from your account so it no longer appears in list_sites (for example test sites). Nothing is deleted: it is the same recoverable archive the dashboard uses. Live sites, and sites with an active client pay link, are refused. Signed-in accounts only. Free.

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_key": "<site_key>"
    },
    "name": "archive_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_keyYesThe site to archive. Must be yours and NOT published (a live site is refused).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only give the coarse destructiveHint=true; the description adds the material nuance that the operation is a recoverable archive identical to the dashboard's, not a deletion, and that it is free and requires sign-in. It also discloses the two refusal conditions (published sites, active client pay link), which annotations cannot express. The tension between destructiveHint=true and "Nothing is deleted" is a refinement of the flag rather than a contradiction of it, though the definition could have been crisper about why the call still counts as destructive.

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?

The core effect and its scope lead the first sentence, and each following clause adds a distinct fact: recoverability, refusal conditions, auth requirement, cost. No sentence restates another, and even the one-word "Free." carries pricing information the agent would otherwise have to guess.

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 one-parameter, no-output-schema tool this covers nearly everything an agent needs: scope, reversibility, refusals, auth, and price. The remaining gap is failure behavior — whether a refusal surfaces as an error and whether re-archiving an already-archived site succeeds (annotations say idempotentHint=false) — which the description leaves unstated.

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% and the single site_key parameter already documents "Must be yours and NOT published (a live site is refused)." The description restates the same ownership/unpublished constraint at the tool level but adds no new syntax, format, or lookup guidance for site_key, so the 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?

Names a specific verb and resource ("Removes one of your own UNPUBLISHED sites from your account") and states the observable effect on a named sibling ("no longer appears in list_sites"). The uppercase UNPUBLISHED plus the parenthetical "for example test sites" makes it distinguishable from publish_site and the create_* siblings at a glance.

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?

Gives clear when-to-use (removing your own test/unpublished sites) and explicit when-not (live sites and sites with an active client pay link are refused), plus the account prerequisite. It stops short of naming an alternative path for the refused cases — an agent told a live site is refused is not told what to do instead — so it is a strong 4 rather than a 5.

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