Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

Draft HTML

get_draft_html
Read-onlyIdempotent

Read back the full HTML of a page's unpublished draft — the work in progress behind its preview URL. Use it before editing a draft you did not write in this conversation: save_draft takes the COMPLETE document and replaces the draft with it, so without reading it first you would rewrite the page from scratch and lose whatever is already there. For the version visitors are actually seeing, use get_published_html.

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>"
    },
    "name": "get_draft_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesThe page whose draft to read, as returned by save_draft or list_pages.

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, idempotentHint and destructiveHint=false, so the safety profile is covered. The description goes further by disclosing the key behavioral risk: save_draft takes the COMPLETE document and replaces the draft, so skipping this read destroys existing work — context an agent could not get from the annotations. It does not describe response shape, but the description already says it returns full HTML.

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?

Three sentences, front-loaded with the purpose, then the usage rationale, then the sibling alternative. Every sentence carries information, though the middle sentence is dense and could be trimmed slightly without loss.

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?

For a one-parameter read tool with strong annotations, the description covers purpose, usage, sibling routing, and the destructive consequence of not using it. No output schema is needed since it states the return is the full HTML document.

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% and the single pageId parameter is fully documented in the schema itself, including its provenance from save_draft or list_pages. The description adds no additional parameter semantics, 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 — 'read back the full HTML of a page's unpublished draft' — and immediately clarifies it is the work-in-progress behind the preview URL. It explicitly contrasts with get_published_html, so an agent can distinguish it from the nearest sibling without opening either schema.

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 an explicit when: before editing a draft you did not write in this conversation. It also names the alternative and its selection condition ('For the version visitors are actually seeing, use get_published_html'), leaving nothing to inference.

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