Skip to main content
Glama

List a project's pages

list_pages
Read-onlyIdempotent

Use this when the founder asks what pages a project has, or you need a page's handle. It returns every hosted page the project has, its landing pages and its post-signup status page, each with whether it is published or still a draft and a link to view it. The link opens the live page when it is published and a temporary preview when it is still a draft. Check it before drafting another page with create_page. Not for a page's blocks or content (use get_page).

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": {
      "project": "<project>"
    },
    "name": "list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesThe project handle, like `prj_…`. From `list_projects`.

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 establish read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful return behavior beyond that: all hosted pages, page types, published/draft status, and whether the link opens a live page or temporary preview. It does not mention pagination or ordering, 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?

The description is front-loaded with the use case and then covers returns, link behavior, and exclusions without wasted preamble. It is slightly longer than strictly necessary because the live/preview link behavior is explained in two sentences, but every part is relevant.

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?

Given the single required parameter and the absence of an output schema, the description is complete enough to use safely: it explains what is returned, how draft versus published links behave, and when to use alternatives. The rich annotations cover safety traits, and the description fills in the missing output context.

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?

There is only one parameter, `project`, and the schema description coverage is 100%, including an example format and provenance from `list_projects`. The description does not add any parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: listing every hosted page a project has, including landing pages and post-signup status pages. It also distinguishes this from `get_page` for blocks/content and from `create_page` for drafting. An agent can identify the tool's purpose without opening the 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 gives explicit when-to-use guidance: when the founder asks what pages a project has, or when a page handle is needed. It also states a concrete alternative: use `get_page` for blocks/content, and use this before drafting another page with `create_page`. This is unusually clear routing.

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.