Skip to main content
Glama

clickup_task_create

Create a new task in a ClickUp list. Optionally set assignees, description, due date, priority, status, or tags and get the task id for subsequent updates.

Instructions

Create a new task in a ClickUp list. The task starts in the list's default status unless 'status' is supplied. Returns the created task object including its new id, which you can pass to clickup_task_update, clickup_task_get, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigneesNoUser IDs to assign to the task. Obtain from clickup_member_list or clickup_user_get. Omit for an unassigned task.
descriptionNoTask body. Markdown supported (headings, links, checkboxes, @mentions). Omit to create the task with no description.
due_dateNoDue date as a Unix timestamp in milliseconds (e.g. 1735689600000 for 2025-01-01). Omit for no due date.
list_idYesID of the list the task will live in. Obtain from clickup_list_list (field: id).
nameYesTask title shown in the list view. Required and non-empty.
priorityNoTask priority: 1=Urgent, 2=High, 3=Normal, 4=Low. Omit for no priority.
statusNoStatus name to start in (case-sensitive; must match a status configured on the list). Omit to use the list's default initial status.
tagsNoTag names to apply. Tags must already exist in the parent space (use clickup_tag_list to see available tags or clickup_tag_create to add new ones).
Behavior4/5

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

Discloses that task starts in default status unless 'status' supplied, and returns created object. With no annotations, it adequately covers key behavior, though does not address permissions or side effects.

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?

Two sentences: purpose first, then behavioral note and return value. No fluff, every sentence serves a purpose.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simple purpose and richness of schema, the description is complete. It names sibling tools for obtaining IDs and mentions return value, which is sufficient for an agent.

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 has 100% coverage for all 8 parameters. Description adds context on default status behavior and return value, supplementing schema without redundancy.

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?

Explicitly states 'Create a new task in a ClickUp list' with verb+resource. Distinguishes from siblings by mentioning return of created task with new id, which can be passed to update/get tools.

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?

Clear context for creation; implies usage when needing a new task. Mentions subsequent use of returned id with other tools, but lacks explicit when-not-to-use or alternatives.

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/nicholasbester/clickup-cli'

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