Skip to main content
Glama

Pagetool

List a site's undo history

list_versions
Read-onlyIdempotent

Lists a site's saved versions, newest first - version_id, why it was saved, its label, whether an AI edit made it (ai: true), and when. Every edit_section and set_theme call saves the page first, so any AI edit can be undone with restore_version. Free, and no account is needed for a draft you created.

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": "list_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of the site, as its path ("/about", "/contact"). Omit for the home page. See list_pages.
site_keyNoThe site whose undo history to list. 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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world behavior, so the safety bar is low; the description still adds real value by disclosing result ordering, the shape of each entry (including the ai:true marker), the fact that every edit_section and set_theme call snapshots the page first, and that listing is free with no account for self-created drafts. It stops short of stating retention limits or how many versions a site accumulates, which is the remaining behavioral unknown.

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 purpose and ordering are front-loaded, and each clause (returned fields, snapshot-on-edit behavior, cost/auth) carries distinct information. It is a single dense sentence, though, which makes the restore_version pointer slightly buried at the end rather than set off as its own line.

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?

There is no output schema, and the description compensates by enumerating the fields each version entry contains, plus ordering and the auth/billing model. For a zero-required-parameter read tool this is nearly sufficient; only retention/volume expectations are left 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 description coverage is 100%, so page, site_key and draft_token are already explained in the schema (path form, default draft site, header fallback). The description adds no parameter-level detail beyond what the schema supplies, 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?

States a specific verb and resource ('Lists a site's saved versions'), adds ordering ('newest first'), and enumerates the returned fields (version_id, reason, label, ai flag, timestamp). It also names the counterpart tool restore_version and the sibling tools that create versions (edit_section, set_theme), so an agent can place it in the workflow without opening a 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?

Usage context is clear: this is the discovery step before restore_version, and the description explicitly says any AI edit 'can be undone with restore_version,' plus notes it is free and works without an account for drafts you created. What is missing is an explicit exclusion or a stated alternative for cases where the caller does not want version history (e.g., list_pages for navigation).

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