Skip to main content
Glama

List Pages

list_pages

Retrieve all pages published by the current user, including each page’s ID, title, URL, and creation date, to review or manage shared HTML links.

Instructions

List all pages published by the current user.

Returns a list of page objects, each with id, title, url, and created_at.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the current-user scoping constraint and the shape of returned objects, which is useful behavioral context, but it says nothing about pagination, result limits, ordering, permissions, or whether unpublished drafts are excluded.

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?

Two short sentences with the scope front-loaded and no wasted wording. The return-shape sentence is somewhat redundant given an output schema exists, but it costs little and is clearly separated.

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?

For a zero-parameter, read-only list tool with an output schema, the description covers purpose, scope, and return shape. The remaining gap is pagination/ordering behavior, which matters for an unbounded listing but is not stated.

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?

The tool takes zero parameters, so the baseline is 4. The description adds nothing that could confuse parameterization; it confirms that listing is unconditional for the current user.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List all pages published by the current user" names a specific verb (list) and resource (pages) and bounds the scope to the current user. It does not explicitly contrast with the mutation siblings (delete_page, publish_page), though the verb makes the read-only intent unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no prerequisites or exclusions. The only context comes from the implicit meaning of "list published by the current user"; an agent must infer on its own that no filtering or pagination options exist.

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

Deploy Server

Other Tools