Skip to main content
Glama

List pages

list_pages
Read-onlyIdempotent

List every page in the maker's space, newest first, with no paging: { total, pages: [{ id, title, url, project, views, live, workEmailGated, hasDraft, comments: { total, open }, createdAt, updatedAt }] }. Read-only. Use it to find a page_id before update_page / get_page / unpublish_page / delete_page, or to reuse an existing project name. Offline pages are included (live: false); deleted pages are not. Pass q to search instead of scanning the full list; use get_page when you need one page's HTML.

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
qNoOptional case-insensitive search over page titles and content. Omit to list everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Optional search query."New value: +"Optional case-insensitive search over page titles and content. Omit to list everything."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them ("Read-only"). It goes well beyond them by disclosing result ordering, the absence of pagination, inclusion of offline pages (live: false), exclusion of deleted pages, and the full field-level shape of each returned page — behavioral facts an agent cannot infer from the annotations.

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?

Front-loaded with purpose and scope, then the return shape, then behavioral caveats, then sibling routing. The inline field listing is dense but earns its place because no output schema exists, and no sentence is redundant.

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?

This is a one-parameter read tool with no output schema, so the description carries the burden of describing the return value — which it does in full field detail. Ordering, filtering, and deletion semantics are all covered, leaving nothing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single q parameter is fully documented there, so the schema baseline of 3 applies. The description still adds value by framing q as the alternative to scanning the full list, which conveys the cost/ordering trade-off the schema text does not.

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?

The description names a specific verb and resource ("List every page in the maker's space"), then adds scope-defining properties: newest first, no paging, and the exact response envelope. It distinguishes itself from search-flavored and single-page siblings (get_page) without requiring the reader to open a schema.

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?

It states the primary use case explicitly (find a page_id before update_page / get_page / unpublish_page / delete_page, or reuse a project name), names the alternative for the search case ("Pass q to search instead of scanning the full list"), and routes to get_page when HTML is required. When-to-use, when-to-use-something-else, and alternatives are all present.

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