Skip to main content
Glama

List hosted pages

list-hosted-pages
Read-only

List the hosted pages (Lead Pages) written for a domain, newest first, optionally by status or review queue. Returns an array with id, slug, page_type, status and published_at; get-hosted-page returns one page with its body, evidence and flagged claims. Requires Lead Pages on the plan.

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": {
      "domain_id": "<domain_id>"
    },
    "name": "list-hosted-pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 25
statusNoawaiting_review lists drafts a reviewer has not rejected. There is no rejected status: rejection returns a page to draft with a reason, and draft lists both.all
domain_idYesDomain ID from list-domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / domain_id / description
      Previous value: -"Domain ID"New value: +"Domain ID from list-domains"
    • changedInput schema / properties / limit / description
      Previous value: -"Max results"New value: +"Max results, default 25"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domain_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Changed1 schema field changed
    • changedInput schema / properties / status / description
      Previous value: -"awaiting_review is an alias for draft, which is where both a new page and a rejected one wait. There is no rejected status: rejection returns a page to draft with a reason."New value: +"awaiting_review lists drafts a reviewer has not rejected. There is no rejected status: rejection returns a page to draft with a reason, and draft lists both."
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, so the description doesn't need to restate safety. It adds genuinely new operational facts: results are ordered newest first and the tool requires Lead Pages on the plan (an entitlement gate the agent cannot see elsewhere). It doesn't discuss pagination or whether limit truncates silently, which is the main 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the listing scope front-loaded before the return fields and the sibling reference. The second sentence packs returns, the alternative, and the plan requirement together, which is dense but each clause earns its place.

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 names the returned fields (id, slug, page_type, status, published_at) and the entitlement prerequisite. It stops short of noting result ordering behavior under filters or whether there is any total/cursor for paging past the 100 limit, which is the only thing an agent might still need.

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 coverage is 100% and the status enum descriptions are unusually thorough (including the 'no rejected status' rule), so the schema carries the load. The description's "optionally by status or review queue" loosely maps the review-queue concept onto awaiting_review but adds no syntax, defaults, or semantics beyond what the schema states.

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 hosted pages (Lead Pages) written for a domain") plus ordering (newest first), and explicitly distinguishes itself from the sibling get-hosted-page. An agent can tell which of the two to call 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative — get-hosted-page — and states what it returns (body, evidence, flagged claims), which implicitly routes the agent there when it needs page content rather than a listing. No explicit "do not use this for X" exclusion, but the split is clear in practice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources