Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

clickup_create_task

Create new tasks in ClickUp with details like name, description, priority, due dates, and assignees to organize project work.

Instructions

Create a new task in ClickUp

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTask name
markdown_descriptionNoTask description in markdown format
list_idYesClickUp list ID
priorityNoTask priority (1-4): 1=Urgent, 2=High, 3=Normal, 4=Low
due_dateNoDue date as Unix timestamp in milliseconds
tagsNoArray of tag names to add to the task
time_estimateNoTime estimate in milliseconds
assigneesNoArray of user IDs to assign to the task
custom_fieldsNoCustom fields to set on task creation
parentNoParent task ID to create this task as a subtask

Implementation Reference

  • The MCP tool handler function that maps input parameters to CreateTaskParams and calls taskService.createTask to execute the task creation, returning the JSON response.
    handler: async (input): Promise<any> => {
      const taskParams: CreateTaskParams = {
        name: input.name,
        list_id: input.list_id,
        markdown_description: input.markdown_description,
        priority: input.priority,
        due_date: input.due_date,
        tags: input.tags,
        time_estimate: input.time_estimate,
        assignees: input.assignees,
        custom_fields: input.custom_fields,
        parent: input.parent,
      };
    
      const response = await taskService.createTask(taskParams);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    },
  • Zod schema defining the input parameters for the clickup_create_task tool.
    inputSchema: {
      name: z.string().describe("Task name"),
      markdown_description: z
        .string()
        .optional()
        .describe("Task description in markdown format"),
      list_id: z.string().describe("ClickUp list ID"),
      priority: z
        .number()
        .optional()
        .describe("Task priority (1-4): 1=Urgent, 2=High, 3=Normal, 4=Low"),
      due_date: z
        .number()
        .optional()
        .describe("Due date as Unix timestamp in milliseconds"),
      tags: z
        .array(z.string())
        .optional()
        .describe("Array of tag names to add to the task"),
      time_estimate: z
        .number()
        .optional()
        .describe("Time estimate in milliseconds"),
      assignees: z
        .array(z.number())
        .optional()
        .describe("Array of user IDs to assign to the task"),
      custom_fields: z
        .array(
          z.object({
            id: z.string().describe("Custom field ID"),
            value: z
              .union([
                z.string(),
                z.number(),
                z.boolean(),
                z.array(z.unknown()),
                z.record(z.unknown()),
              ])
              .describe("Value for the custom field"),
          })
        )
        .optional()
        .describe("Custom fields to set on task creation"),
      parent: z
        .string()
        .optional()
        .describe("Parent task ID to create this task as a subtask"),
    },
  • src/index.ts:89-91 (registration)
    Registration of the clickup_create_task tool (along with others) to the MCP server using server.tool.
    tools.forEach((tool) => {
      server.tool(tool.name, tool.description, tool.inputSchema, tool.handler);
    });
  • The TaskService.createTask method that performs the actual HTTP POST request to the ClickUp API to create the task.
    async createTask(params: CreateTaskParams): Promise<ClickUpTask> {
      const { list_id, ...taskData } = params;
    
      return this.request<ClickUpTask>(`/list/${list_id}/task`, {
        method: "POST",
        body: JSON.stringify(taskData),
      });
    }
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. While 'Create' implies a write operation, it doesn't mention authentication requirements, rate limits, error conditions, or what happens on success (e.g., returns a task ID). For a mutation tool with 10 parameters, 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 states the core purpose without unnecessary words. It's appropriately sized for what it communicates, though it could benefit from additional context.

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 complex mutation tool with 10 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, error conditions, or behavioral constraints. The agent would need to guess about the response format and operational boundaries.

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 schema description coverage is 100%, with each parameter well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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 ('Create') and resource ('new task in ClickUp'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'clickup_update_task' or other task-related tools, which would require mentioning this is specifically for initial creation rather than modification.

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 about when to use this tool versus alternatives like 'clickup_update_task' or 'clickup_create_doc'. There's no mention of prerequisites (like needing a list_id) or typical use cases, leaving the agent to infer usage from the parameter schema 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