Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

clickup_get_page

Retrieve specific pages from ClickUp documents using document and page IDs to access workspace content.

Instructions

Get a page from a ClickUp doc

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_idYesClickUp doc ID
page_idYesClickUp page ID

Implementation Reference

  • Core implementation of fetching a ClickUp page by making an API GET request to the ClickUp API endpoint.
    async getPage(docId: string, pageId: string): Promise<ClickUpDocPage> {
      return this.request<ClickUpDocPage>(
        `/${this.workspaceId}/docs/${docId}/pages/${pageId}`
      );
    }
  • Defines and registers the 'clickup_get_page' MCP tool, including Zod input schema and a thin handler wrapper that delegates to DocsService.getPage and formats the response.
    const getPageTool = defineTool((z) => ({
      name: "clickup_get_page",
      description: "Get a page from a ClickUp doc",
      inputSchema: {
        doc_id: z.string().describe("ClickUp doc ID"),
        page_id: z.string().describe("ClickUp page ID"),
      },
      handler: async (input) => {
        const response = await docsService.getPage(input.doc_id, input.page_id);
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      },
    }));
  • Zod input schema for the tool defining doc_id and page_id parameters.
      inputSchema: {
        doc_id: z.string().describe("ClickUp doc ID"),
        page_id: z.string().describe("ClickUp page ID"),
      },
      handler: async (input) => {
        const response = await docsService.getPage(input.doc_id, input.page_id);
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      },
    }));
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Get a page' but doesn't clarify if this is a read-only operation, what permissions are required, whether it returns content or metadata, or any rate limits. The description lacks behavioral traits beyond the basic action, leaving significant gaps for an agent to understand how to use it effectively.

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 with no wasted words. It's front-loaded with the core action and resource, making it easy to parse. Every part of the sentence contributes directly to understanding the tool's purpose.

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 moderate complexity (retrieving a specific page), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'Get' returns (e.g., page content, metadata, or both), any error conditions, or behavioral context. This leaves the agent with insufficient information to use the tool correctly beyond basic parameter passing.

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 both parameters ('doc_id' and 'page_id') clearly documented as ClickUp IDs. The description doesn't add any meaning beyond this, such as where to find these IDs or format requirements. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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') and resource ('a page from a ClickUp doc'), making the purpose understandable. It distinguishes from siblings like 'clickup_get_doc_pages' (which lists pages) and 'clickup_edit_page' (which modifies pages), though it doesn't explicitly name these alternatives. The verb+resource combination is specific but could be more precise about what 'Get' entails.

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 prerequisites (e.g., needing a doc and page ID), exclusions, or compare it to siblings like 'clickup_get_doc_pages' for listing pages or 'clickup_search_docs' for finding docs. Usage is implied by the name 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