Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

clickup_create_page

Create a new page in a ClickUp document by specifying the doc ID, page name, and markdown content. Add subtitles and organize pages hierarchically with parent page IDs.

Instructions

Create a new page in a ClickUp doc

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_idYesClickUp doc ID
nameYesPage name
parent_page_idNoParent page ID (null for root page)
sub_titleNoPage subtitle
contentYesPage content in markdown format

Implementation Reference

  • MCP tool definition for 'clickup_create_page', including name, description, input schema (Zod), and handler function that prepares parameters and delegates to docsService.createPage, returning JSON response.
    const createPageTool = defineTool((z) => ({
      name: "clickup_create_page",
      description: "Create a new page in a ClickUp doc",
      inputSchema: {
        doc_id: z.string().describe("ClickUp doc ID"),
        name: z.string().describe("Page name"),
        parent_page_id: z
          .string()
          .optional()
          .describe("Parent page ID (null for root page)"),
        sub_title: z.string().optional().describe("Page subtitle"),
        content: z.string().describe("Page content in markdown format"),
      },
      handler: async (input) => {
        const pageParams: CreatePageParams = {
          docId: input.doc_id,
          name: input.name,
          parent_page_id: input.parent_page_id,
          sub_title: input.sub_title,
          content: input.content,
        };
        const response = await docsService.createPage(pageParams);
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      },
    }));
  • src/index.ts:29-62 (registration)
    The createPageTool is included in the 'tools' array which is iterated over to register all tools with the MCP server using server.tool(tool.name, tool.description, tool.inputSchema, tool.handler).
    const tools = [
      // Task tools
      getTaskByCustomIdTool,
      getTaskTool,
      createTaskTool,
      updateTaskTool,
      updateTaskByCustomIdTool,
    
      // Space tools
      getSpacesTool,
    
      // Folder tools
      getFoldersTool,
    
      // List tools
      getListsTool,
      createListTool,
    
      // Custom Field tools
      getListCustomFieldsTool,
      setCustomFieldValueTool,
      setCustomFieldValueByCustomIdTool,
    
      // Assignee tools
      getListAssigneesTool,
    
      // Docs tools
      searchDocsTool,
      createDocTool,
      getDocPagesTool,
      getPageTool,
      createPageTool,
      editPageTool,
    ];
  • Core implementation of page creation: constructs the request payload and performs POST API call to ClickUp to create the page.
    async createPage(params: CreatePageParams): Promise<ClickUpDocPage> {
      const { docId, name, parent_page_id, sub_title, content } = params;
      const pageData = {
        name,
        parent_page_id: parent_page_id || null,
        sub_title: sub_title || null,
        content,
        content_format: "text/md",
      };
    
      return this.request<ClickUpDocPage>(
        `/${this.workspaceId}/docs/${docId}/pages`,
        {
          method: "POST",
          body: JSON.stringify(pageData),
        }
      );
    }
  • TypeScript interface defining the parameters for creating a ClickUp page, used in the tool handler and service method.
    export interface CreatePageParams {
      docId: string;
      name: string;
      parent_page_id?: string;
      sub_title?: string;
      content: string;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation (implying mutation/write), but doesn't mention required permissions, whether it's idempotent, error conditions, or what happens on success (e.g., returns page ID). For a write tool with zero annotation coverage, this leaves significant behavioral gaps.

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 communicates the core purpose without unnecessary words. It's appropriately sized for a straightforward creation tool and front-loads the essential information ('Create a new page in a ClickUp doc').

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?

For a write operation with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., returns page ID), error handling, or system behavior. Given the complexity of creating a page with 5 parameters and 3 required fields, more contextual information would help the agent use this tool effectively.

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?

Schema description coverage is 100%, providing good documentation for all 5 parameters. The description adds no parameter-specific information beyond what's in the schema (e.g., it doesn't clarify format expectations or provide examples). With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't enhance parameter 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 ('Create a new page') and resource ('in a ClickUp doc'), making the purpose immediately understandable. It distinguishes from obvious siblings like 'clickup_create_doc' (creates docs vs pages) and 'clickup_edit_page' (edits vs creates), though it doesn't explicitly differentiate from all siblings.

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 an existing doc), compare to similar tools like 'clickup_create_doc', or indicate when not to use it. The agent must infer usage from the tool name alone.

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