Skip to main content
Glama

create_task

Create tasks in ClickUp by name or list ID, with optional status, priority, and due date settings.

Instructions

Create a new task in ClickUp. Supports direct name-based lookup for lists - no need to know the list ID. -Status will use ClickUp defaults if not specified. If the specified list doesn't exist, you can create it using create_list or create_list_in_folder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdNoID of the list to create the task in (optional if using listName instead)
listNameNoName of the list to create the task in - will automatically find the list by name (optional if using listId instead)
nameYesName of the task
descriptionNoPlain text description for the task
markdown_descriptionNoMarkdown formatted description for the task. If provided, this takes precedence over description
statusNoOPTIONAL: Override the default ClickUp status. In most cases, you should omit this to use ClickUp defaults
priorityNoPriority of the task (1-4), 1 is highest priority, 4 is lowest priority. -If not specified, the task will not set a priority.
dueDateNoDue date of the task (Unix timestamp in milliseconds)
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that status defaults to ClickUp default and markdown_description takes precedence. However, it does not discuss return values, error handling, or side effects, leaving 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 concise with two efficient sentences. It front-loads the core purpose and then adds critical usage details. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 and no output schema, the description covers core functionality but omits return value details and error handling. It is adequate but could be more complete for a creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, setting baseline at 3. The description adds value by explaining the automatic name-based lookup and the precedence of markdown_description, which goes beyond the schema's basic descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a new task in ClickUp' with specific verb and resource. It highlights the unique feature of name-based list lookup, distinguishing it from other task creation tools. The mention of default status and fallback to create_list further clarifies its scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides guidance on when to use this tool (e.g., using name-based lookup) and suggests alternatives (create_list or create_list_in_folder) when list doesn't exist. It also advises when to omit status. However, it does not explicitly differentiate from create_bulk_tasks.

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/mikepsinn/clickup-mcp-server'

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