Skip to main content
Glama

list_pages

Retrieve a paginated listing of wiki pages accessible to the user, with options to sort results and control page size for efficient content browsing.

Instructions

Get a listing of pages visible to the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
countNoNumber of items per page
sortNoSort parameter

Implementation Reference

  • Handler logic for the 'list_pages' tool: parses input arguments using PaginationSchema, calls BookStackClient.getPages with pagination params, and formats the paginated response using formatApiResponse.
    case "list_pages": {
      const params = PaginationSchema.parse(args);
      const result = await client.getPages(params);
      return formatApiResponse(result.data, result.total);
    }
  • Tool definition including name, description, and input schema for 'list_pages', specifying optional pagination parameters (page, count, sort).
    {
      name: "list_pages",
      description: "Get a listing of pages visible to the user",
      inputSchema: {
        type: "object",
        properties: {
          page: { type: "number", description: "Page number for pagination" },
          count: { type: "number", description: "Number of items per page" },
          sort: { type: "string", description: "Sort parameter" },
        },
      },
    },
  • src/index.ts:124-126 (registration)
    Registers 'list_pages' for execution by checking if the tool name is in contentToolNames (which includes 'list_pages') and dispatching to handleContentTool.
    if (contentToolNames.includes(name)) {
      result = await handleContentTool(name, args, bookStackClient);
    } else if (searchUserToolNames.includes(name)) {
  • src/index.ts:56-59 (registration)
    Registers the 'list_pages' tool schema by including createContentTools output in the allTools array returned by the MCP listTools handler.
    const allTools: Tool[] = [
      ...createContentTools(bookStackClient),
      ...createSearchAndUserTools(bookStackClient),
    ];
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves a listing but omits critical details like whether it's paginated (implied by parameters but not described), what the output format is, rate limits, authentication needs, or error conditions. For a read operation with zero annotation coverage, this is insufficient.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence contributes meaning, earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a listing tool with pagination and sorting parameters, no annotations, and no output schema, the description is incomplete. It fails to explain the return format, pagination behavior, or how visibility filtering works, leaving significant gaps for an agent to understand the tool's full behavior.

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?

The input schema has 100% description coverage, with clear parameter descriptions for 'page', 'count', and 'sort'. The description adds no additional semantic context about these parameters, such as default values, valid ranges, or how 'sort' works. Baseline 3 is appropriate since the schema does the heavy lifting, but the description doesn't enhance understanding.

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?

The description clearly states the action ('Get a listing') and resource ('pages'), specifying that it retrieves pages 'visible to the user', which adds useful context about scope. However, it doesn't explicitly differentiate from sibling tools like 'list_books' or 'list_chapters' beyond the resource name, missing an opportunity to clarify what makes listing pages distinct.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_page' (for single pages) or 'search_all' (for broader searches), nor does it specify prerequisites or contexts for usage. This leaves the agent without direction on tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lautarobarba/bookstack_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server