Skip to main content
Glama

get_page

Retrieve content and details for a specific page using its ID to access information from a BookStack wiki instance.

Instructions

Get details and content of a specific page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPage ID

Implementation Reference

  • The handler function for the 'get_page' tool. It parses the page ID from arguments, calls the BookStack client's getPage method, and formats the API response.
    case "get_page": {
      const id = parseInteger(args.id);
      const result = await client.getPage(id);
      return formatApiResponse(result);
    }
  • The tool definition including name, description, and input schema for validating the 'id' parameter as a required number.
    {
      name: "get_page",
      description: "Get details and content of a specific page",
      inputSchema: {
        type: "object",
        properties: {
          id: { type: "number", description: "Page ID" },
        },
        required: ["id"],
      },
    },
  • src/index.ts:56-59 (registration)
    Registration of tools by combining content tools (which includes 'get_page') into the allTools array provided to the MCP server.
    const allTools: Tool[] = [
      ...createContentTools(bookStackClient),
      ...createSearchAndUserTools(bookStackClient),
    ];
  • src/index.ts:124-126 (registration)
    Dispatch registration: routes calls to 'get_page' (listed in contentToolNames) to the handleContentTool function.
    if (contentToolNames.includes(name)) {
      result = await handleContentTool(name, args, bookStackClient);
    } else if (searchUserToolNames.includes(name)) {
  • Helper method in BookStackClient that performs the actual API GET request to retrieve a page by ID.
    async getPage(id: number): Promise<Page> {
      const response: AxiosResponse<Page> = await this.api.get(`/pages/${id}`);
      return response.data;
    }
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 it 'gets details and content,' implying a read-only operation, but does not specify aspects like authentication needs, rate limits, error handling, or return format. This leaves significant gaps for a tool with no annotation support.

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 function without unnecessary words. It is front-loaded and appropriately sized for its purpose, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It does not explain what 'details and content' includes, how results are structured, or any behavioral traits like safety or performance. For a retrieval tool in a context with many siblings, more context is needed to guide effective use.

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 the 'id' parameter clearly documented as 'Page ID.' The description does not add any extra meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without compensation.

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 verb ('Get') and resource ('details and content of a specific page'), making the purpose understandable. However, it does not differentiate from sibling tools like 'get_book' or 'get_chapter', which have similar retrieval purposes for different resources, so it lacks sibling distinction.

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, such as 'list_pages' for browsing or 'search_all' for broader queries. There is no mention of prerequisites, exclusions, or contextual usage, leaving the agent with minimal direction.

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