Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

clickup_create_doc

Create a new document in ClickUp by specifying a name and parent location, with options to set visibility and include an initial page.

Instructions

Create a new doc in ClickUp

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the new Doc
parentYesParent object
visibilityNoDoc visibility (PUBLIC or PRIVATE), PRIVATE by default
create_pageNoWhether to create a initial page (false by default)

Implementation Reference

  • Defines the MCP tool 'clickup_create_doc' including its name, description, Zod input schema, and async handler function. The handler maps input to CreateDocParams, calls DocsService.createDoc, and returns a JSON-formatted response.
    const createDocTool = defineTool((z) => ({
      name: "clickup_create_doc",
      description: "Create a new doc in ClickUp",
      inputSchema: {
        name: z.string().describe("The name of the new Doc"),
        parent: z
          .object({
            id: z.string().describe("Parent ID"),
            type: z
              .number()
              .describe(
                "Parent type: 4 for Space, 5 for Folder, 6 for List, 7 for Everything, 12 for Workspace"
              ),
          })
          .describe("Parent object"),
        visibility: z
          .string()
          .optional()
          .describe("Doc visibility (PUBLIC or PRIVATE), PRIVATE by default"),
        create_page: z
          .boolean()
          .optional()
          .describe("Whether to create a initial page (false by default)"),
      },
      handler: async (input) => {
        const docParams: CreateDocParams = {
          name: input.name,
          parent: input.parent,
          visibility: input.visibility,
          create_page: input.create_page,
        };
        const response = await docsService.createDoc(docParams);
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      },
    }));
  • Core helper method in DocsService that handles the actual API interaction: prepares request data with defaults and performs POST to ClickUp's /workspaces/{workspaceId}/docs endpoint.
    async createDoc(params: CreateDocParams): Promise<ClickUpDoc> {
      const docData = {
        name: params.name,
        parent: params.parent,
        visibility: params.visibility || "PRIVATE",
        create_page:
          params.create_page !== undefined ? params.create_page : false,
      };
    
      return this.request<ClickUpDoc>(`/${this.workspaceId}/docs`, {
        method: "POST",
        body: JSON.stringify(docData),
      });
    }
  • TypeScript interface defining the input parameters for creating a ClickUp doc, used for type safety in the service and controller.
    export interface CreateDocParams {
      name: string;
      parent: {
        id: string;
        type: number; // 4 for Space, 5 for Folder, 6 for List, 7 for Everything, 12 for Workspace
      };
      visibility?: string; // "PRIVATE" by default
      create_page?: boolean; // false by default
    }
  • src/index.ts:55-62 (registration)
    Includes the createDocTool in the 'tools' array alongside other doc-related tools.
      // Docs tools
      searchDocsTool,
      createDocTool,
      getDocPagesTool,
      getPageTool,
      createPageTool,
      editPageTool,
    ];
  • src/index.ts:89-91 (registration)
    Loop that registers every tool in the 'tools' array (including clickup_create_doc) with the MCP server instance by calling server.tool().
    tools.forEach((tool) => {
      server.tool(tool.name, tool.description, tool.inputSchema, tool.handler);
    });
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 'Create' which implies a write/mutation operation, but doesn't mention required permissions, whether the operation is idempotent, error conditions, or what happens on success. For a creation tool with zero annotation coverage, this is a significant gap in behavioral context.

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 states the core function without any wasted words. It's appropriately sized for a straightforward creation tool and gets directly to the point.

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 creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'doc' is in ClickUp's context, what gets returned upon creation, or any behavioral aspects. Given the complexity (4 parameters including nested objects) and lack of structured metadata, the description should provide more context about the operation.

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%, so the schema already documents all 4 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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') and resource ('new doc in ClickUp'), making the purpose immediately understandable. It doesn't differentiate from siblings like clickup_create_page or clickup_create_task, which would require specifying what distinguishes a 'doc' from a 'page' or 'task' in ClickUp's terminology.

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?

No guidance is provided on when to use this tool versus alternatives like clickup_create_page or clickup_create_task. The description gives no context about prerequisites, appropriate scenarios, or exclusions, leaving the agent to 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