Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

clickup_get_doc_pages

Retrieve pages from a ClickUp document by providing its ID to access content within the workspace.

Instructions

Get pages from a ClickUp doc

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_idYesClickUp doc ID

Implementation Reference

  • Defines the 'clickup_get_doc_pages' MCP tool, including input schema, description, and handler function that calls the DocsService to fetch pages and returns JSON response.
    const getDocPagesTool = defineTool((z) => ({
      name: "clickup_get_doc_pages",
      description: "Get pages from a ClickUp doc",
      inputSchema: {
        doc_id: z.string().describe("ClickUp doc ID"),
      },
      handler: async (input) => {
        const response = await docsService.getDocPages(input.doc_id);
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      },
    }));
  • Core helper method in DocsService that makes the API request to retrieve pages from a specific ClickUp doc.
    async getDocPages(docId: string): Promise<{ pages: ClickUpDocPage[] }> {
      return this.request<{ pages: ClickUpDocPage[] }>(
        `/${this.workspaceId}/docs/${docId}/pageListing`
      );
    }
  • src/index.ts:89-91 (registration)
    Registers all MCP tools, including 'clickup_get_doc_pages', by iterating over the tools array and calling server.tool() with the tool's properties.
    tools.forEach((tool) => {
      server.tool(tool.name, tool.description, tool.inputSchema, tool.handler);
    });
  • src/index.ts:12-18 (registration)
    Imports the getDocPagesTool from docs.controller for registration in the MCP server.
      searchDocsTool,
      createDocTool,
      getDocPagesTool,
      getPageTool,
      createPageTool,
      editPageTool,
    } from "./controllers/docs.controller";
  • src/index.ts:55-62 (registration)
    Adds getDocPagesTool to the central tools array used for MCP server registration.
      // Docs tools
      searchDocsTool,
      createDocTool,
      getDocPagesTool,
      getPageTool,
      createPageTool,
      editPageTool,
    ];
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get pages' which implies a read-only operation, but doesn't disclose behavioral traits such as whether it returns all pages or paginated results, error conditions (e.g., invalid doc_id), rate limits, or authentication needs. The description is minimal and leaves key behaviors unspecified.

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 a single, efficient sentence with no wasted words. It's appropriately sized for a simple tool, though it could be more front-loaded with key details. The brevity is good, but it borders on under-specification given the lack of annotations.

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 tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It doesn't explain what 'pages' are in ClickUp's context, the return format, or error handling. For a tool with no structured output or annotations, more descriptive 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 single parameter 'doc_id' documented as 'ClickUp doc ID'. The description adds no additional meaning beyond this, such as format examples or where to find the ID. With high schema coverage, the baseline is 3, and the description doesn't compensate with extra context.

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

Purpose3/5

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

The description 'Get pages from a ClickUp doc' clearly states the verb ('Get') and resource ('pages from a ClickUp doc'), but it's vague about what 'pages' means in this context and doesn't distinguish it from sibling tools like 'clickup_get_page' (singular) or 'clickup_search_docs'. It provides basic purpose but lacks specificity.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over 'clickup_get_page' (for a single page) or 'clickup_search_docs' (for broader document searches), nor does it specify prerequisites like needing a valid doc_id. Usage is implied but not explicitly stated.

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/Leanware-io/clickup-mcp-server'

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