Skip to main content
Glama

create_task

Add new tasks to ClickUp lists by specifying list ID, task name, description, assignees, and due date to organize work.

Instructions

Create a new task in a ClickUp list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesClickUp List ID
nameYesTask name
descriptionNoTask description
assigneesNoArray of assignee user IDs
due_dateNoDue date in Unix timestamp (milliseconds)

Implementation Reference

  • The asynchronous handler function that implements the create_task tool. It constructs task data from arguments and posts it to the ClickUp API to create a new task, returning the response or an error.
    const createTask = async (args: any) => {
      try {
        const taskData: any = {
          name: args.name,
        };
        if (args.description) taskData.description = args.description;
        if (args.assignees) taskData.assignees = args.assignees;
        if (args.due_date) taskData.due_date = parseInt(args.due_date);
        const response = await clickupApi.post(`/list/${args.list_id}/task`, taskData);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          return {
            content: [
              {
                type: "text",
                text: `ClickUp API error: ${error.response?.data?.err ?? error.message}`,
              },
            ],
            isError: true,
          };
        }
        throw error;
      }
    };
  • The input schema and description for the create_task tool, defined within the server's capabilities.
    create_task: {
      description: "Create a new task in a ClickUp list",
      inputSchema: {
        type: "object",
        properties: {
          list_id: {
            type: "string",
            description: "ClickUp List ID"
          },
          name: {
            type: "string",
            description: "Task name"
          },
          description: {
            type: "string",
            description: "Task description"
          },
          assignees: {
            type: "array",
            items: { type: "number" },
            description: "Array of assignee user IDs"
          },
          due_date: {
            type: "string",
            description: "Due date in Unix timestamp (milliseconds)"
          }
        },
        required: ["list_id", "name"]
      }
    },
  • src/index.ts:279-294 (registration)
    The CallToolRequestHandler registration where the create_task tool is dispatched by calling the createTask handler function based on the tool name.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      // @ts-ignore
      const { name, arguments: args } = request.params;
      switch (name) {
        case 'get_tasks':
          return await getTasks(args);
        case 'create_task':
          return await createTask(args);
        case 'update_task':
          return await updateTask(args);
        case 'get_task':
          return await getTask(args);
        default:
          throw new Error(`Unknown tool: ${name}`);
      }
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Create a new task,' implying a write/mutation operation, but fails to disclose critical traits such as required permissions, whether the operation is idempotent, error handling, or any rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loads the core action ('Create a new task') and specifies the context ('in a ClickUp list') without any wasted words. It is appropriately sized for a straightforward tool, making it easy for an agent to parse quickly.

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 complexity as a mutation operation with no annotations and no output schema, the description is incomplete. It lacks information on behavioral aspects (e.g., permissions, side effects), usage guidelines, and what the tool returns. For a create tool with 5 parameters and significant implications, the description should provide more context to aid the agent 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?

The schema description coverage is 100%, meaning all parameters are documented in the input schema (e.g., 'list_id' as ClickUp List ID, 'due_date' in Unix timestamp). The description adds no additional semantic context beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't detract either.

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 a ClickUp list'), making the purpose immediately understandable. It distinguishes from siblings like 'get_task' or 'update_task' by specifying creation. However, it doesn't explicitly mention what distinguishes it from other potential creation tools beyond the ClickUp context, keeping it from a perfect score.

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 like 'update_task' or other task management operations. It lacks context about prerequisites (e.g., needing an existing list), exclusions, or typical scenarios for task creation, leaving the agent to infer usage from the name and 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/rubenaguir/clickup-mcp-server'

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