Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

Page information

get_page_information
Read-onlyIdempotent

Look up one page and what state it is in: whether it is published and at which version, and whether it has an unpublished draft with a preview URL. CALL THIS BEFORE EDITING a page you did not just create — if a draft is already open, saving replaces it, so you need to know whether it holds work the user still wants. Accepts anything that identifies the page: its pageId, its slug, its Pageree URL, a connected custom domain, or a draft preview URL.

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": {
      "page": "<page>"
    },
    "name": "get_page_information"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesThe pageId, slug, page URL, custom domain, or draft preview URL. Scheme and path are ignored, so a URL the user pasted works as-is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 safety is covered; the description adds genuinely non-obvious context about a downstream risk (an open draft gets overwritten on save). It also documents the permissive identifier handling. It doesn't discuss error behavior for a nonexistent page, which keeps it from a 5.

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?

Three sentences, front-loaded with what is returned, then the call-before-editing rule, then input flexibility. No filler; every sentence carries a distinct fact.

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?

No output schema exists, and the description compensates by enumerating the relevant returned state (published flag, version, draft presence, preview URL). Combined with readOnly annotations and a fully documented single parameter, an agent has everything needed to call it correctly.

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?

With one parameter at 100% schema coverage, the schema already documents the accepted identifier types and that scheme/path are ignored. The description's enumeration largely restates that, adding only marginal meaning beyond the structured field.

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 ("Look up one page") plus the exact information returned: publication status, version, and whether an unpublished draft with a preview URL exists. This clearly separates it from list_pages (enumeration), get_published_html/get_draft_html (content), and list_versions (history).

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?

Gives an explicit imperative and condition: "CALL THIS BEFORE EDITING a page you did not just create," with the rationale that an existing draft would be replaced. It stops short of naming the alternatives it competes with (get_draft_html, get_published_html, list_versions), so it falls just below the when/when-not/alternatives standard.

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