Skip to main content
Glama

Pagetool

Drop staged changes

discard_staged
Idempotent

Drops a site's staged changes without touching the live site. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discard_staged"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_keyNoThe site whose staged changes should be dropped. Defaults to the caller's current draft site when omitted.
draft_tokenNoThe draft token returned by draft_create, if you are working on an anonymous draft. Only needed when your client cannot send the x-pagetool-draft-token header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, and the description earns credit by explaining WHY it is non-destructive: it only affects staged changes, not the live site. It also adds a cost signal ('Free') that annotations do not carry. The remaining gap is reversibility — it never says whether dropped changes can be recovered or whether the draft site survives the drop.

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 with zero filler; the non-destructive guarantee is front-loaded right after the verb, and 'Free' is a single word that carries real decision value for an agent weighing a discard action.

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?

For a two-parameter, zero-required mutation with no output schema, the definition covers what is affected and what is not, but leaves open what the call returns (confirmation object? empty response?) and whether the staged draft remains addressable afterward. Those are modest but real gaps for a discard 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 description coverage is 100%, with site_key's default (caller's current draft site) and draft_token's header fallback both documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb (drops) and resource (a site's staged changes) and immediately bounds the scope with 'without touching the live site', which is exactly the distinction that matters against the sibling publish_staged. It stops short of naming that sibling or any other alternative, so differentiation is achieved by contrast rather than explicit routing.

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

Usage Guidelines3/5

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

The use case (abandon staged work, leave the live site intact) is implied clearly enough to infer when to call it, but there is no explicit 'use when' clause, no mention of when NOT to use it, and no pointer to publish_staged or the draft_* tools as the alternative paths.

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