Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

Previous version HTML

get_previous_version_html
Read-onlyIdempotent

Read back the full HTML of an EARLIER published version of a page. Versions are immutable, so this is what that version actually shipped. Two uses: recovering something an later edit removed without rolling the whole page back, and the optimize loop — read the version that converted better, compare it against the live one from get_published_html, and see what the change actually was. Use list_versions to find the label. To make an old version live again, that is rollback, not this.

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": {
      "pageId": "<pageId>",
      "version": "<version>"
    },
    "name": "get_previous_version_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesThe page to read, as returned by list_pages.
versionYesThe version label to read, e.g. "v2". Use list_versions to see what exists.

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 readOnly/idempotent/non-destructive, so the safety profile is covered. The description still adds real context: versions are immutable, so the returned HTML is exactly what shipped, and re-publishing an old version is explicitly out of scope. It does not cover what happens on a bad version label, but the added immutability semantics are the valuable part.

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?

Front-loads the core read operation, then use cases, then the rollback exclusion — good ordering with no filler. Minor deduction for a typo ('an later edit') and for packing the two use cases into one dense sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Two required params, fully described in schema, no output schema needed since the description says it returns full HTML. An agent has everything required to select and invoke it correctly without reading sibling definitions.

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 both pageId and version are already documented, and the 'use list_versions' hint merely restates the schema's own note. No additional syntax or format detail is added beyond the structured data, so 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 ('Read back the full HTML of an EARLIER published version of a page'), capitalized to distinguish it from live content. It is immediately distinguishable from get_published_html, get_draft_html, and rollback, which are named directly.

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 two concrete uses (recovering removed content without a full rollback, and the optimize-loop comparison against get_published_html) plus the prerequisite step (list_versions for the label). It also explicitly excludes the rollback path — this tool does not make a version live — so an agent cannot confuse the two.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pageree toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources