Skip to main content
Glama
Sign In

Pageree

by com.pageree
OverviewDiscussionsAdmin

List pages

list_pages
Read-onlyIdempotent

List the account's landing pages, most recently touched first: pageId, slug, live URL, current version, and whether each has an unpublished draft. Use it when you do not know a pageId — a new conversation, a lost .pageree file, or a user who refers to a page by name. Then pass the pageId to get_page_information or save_draft. A page showing a draft has work in progress that nobody has published; worth telling the user about.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many pages to return (default 25, max 100).
offsetNoHow many to skip, for accounts with more pages than one page of results.

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, closed-world behavior, so the description is free to add the ordering guarantee (most recently touched first) and an interpretation of draft state that the agent should surface to the user. It does not mention total counts or whether more results exist beyond limit/offset, which is the remaining gap.

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 the resource and return shape, then the usage trigger, then the actionable draft caveat. No filler; each sentence carries distinct information.

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?

With no output schema, the description usefully enumerates the returned fields and explains the draft flag, and the schema covers pagination. It stops short of saying whether the response indicates more pages remain, which would close the last ambiguity for a list tool.

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 both parameters (limit with default 25/max 100, offset) are fully documented there. The description adds only the ordering context that makes limit/offset meaningful, but no additional parameter semantics, so the baseline 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 (list the account's landing pages) plus the exact fields returned (pageId, slug, live URL, current version, draft status) and the sort order. It is clearly distinguishable from get_page_information, which requires a pageId the caller does not yet have.

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 explicit triggering conditions (unknown pageId, new conversation, lost .pageree file, user refers to a page by name) and names the follow-on tools (get_page_information, save_draft) to call with the returned pageId. This is exactly the when-to-use and what-next guidance an agent needs.

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