Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

Published HTML

get_published_html
Read-onlyIdempotent

Read back the full HTML of the version a page is LIVE with right now. This is the starting point for editing any page you did not build in this conversation: save_draft takes the COMPLETE document, so to change one heading you need the other 900 lines to send back with it. Read this, make the edit, then save_draft the whole thing. Returns the stored source, so it carries no analytics pixel — never add one. If the page has an open draft, that is newer than this; read it with get_draft_html instead.

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_published_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesThe page to read, as returned by publish, list_pages or get_page_information.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real behavioral context: the return is the stored source with no analytics pixel ('never add one'), and draft state can supersede what you read. These are non-obvious traits an agent could not infer from the annotation block.

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?

Purpose is front-loaded and every sentence carries signal. The save_draft rationale is slightly over-explained ('to change one heading you need the other 900 lines' then 'save_draft the whole thing'), which is useful framing but costs a sentence beyond what the routing logic needs.

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?

Though there is no output schema, the description explicitly characterizes the return ('the stored source') and even its deficiency (no analytics pixel). Combined with the workflow into save_draft, an agent has everything needed to call this correctly in sequence.

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?

Only one parameter, and its schema description is already 100% covered, including where the pageId comes from (publish, list_pages, get_page_information). The description adds nothing about the parameter itself, 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 with precise scope: 'Read back the full HTML of the version a page is LIVE with right now.' The phrase 'LIVE' immediately separates it from get_draft_html and get_previous_version_html without needing either schema opened.

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 triggering condition ('the starting point for editing any page you did not build in this conversation') and names the alternative with its own condition ('If the page has an open draft, that is newer than this; read it with get_draft_html instead'). This is exactly the when/when-not/alternative structure.

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