Skip to main content
Glama

List site pages

list-site-pages
Read-only

List the pages discovered for a domain, sorted by URL, with their latest audit. Returns {data, next_cursor, has_more}; items have id, url, tracked, issues and scores (technical, content, aeo). Tracked page ids are what run-site-audit takes; list-site-audits lists individual audits.

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-site-pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoCursor for next page (echo next_cursor from prior response)
limitNoPage size, default 25
domain_idYesDomain ID from list-domains
page_typeNoFilter by page type

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: +"Page size, 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. 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 readOnlyHint=true and destructiveHint=false, so the description correctly spends its budget elsewhere: sort order, the {data, next_cursor, has_more} envelope, and item fields. That pagination and return-shape disclosure is real added value beyond the annotations, though rate limits or filtering behavior are unmentioned.

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 tightly packed sentences with zero filler: purpose and ordering first, then return shape, then sibling disambiguation. Every clause carries information an agent would otherwise have to infer.

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 naming the response envelope and item fields. Combined with full schema coverage and explicit sibling routing, an agent has everything needed to call this 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?

Schema description coverage is 100%, so every parameter is already documented in the schema (after, limit, domain_id, page_type enum). The description adds no parameter-level semantics beyond the concept of tracking page ids, so 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 ('List the pages discovered for a domain'), plus ordering ('sorted by URL') and the payload shape including id, url, tracked, issues and scores. It also explicitly distinguishes itself from list-site-audits and run-site-audit, so an agent can route 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?

Provides clear context linking to alternatives: 'Tracked page ids are what run-site-audit takes; list-site-audits lists individual audits' tells the agent when to use each sibling. It stops short of explicit when-not-to-use or prerequisite guidance (e.g. needing a domain_id from list-domains is only in the schema).

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