Skip to main content
Glama
azukhrufy
by azukhrufy

create_task

Create a new task in a ClickUp list, setting assignees, due date, priority, status, and custom fields as needed.

Instructions

Create a new task in a ClickUp list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the task
tagsNoTags to add to the task
parentNoParent task ID to make this a subtask
statusNoStatus of the task
list_idYesThe ID of the list
due_dateNoDue date as ms timestamp
links_toNoTask ID to link this task to
priorityNoPriority: 1=Urgent, 2=High, 3=Normal, 4=Low
assigneesNoArray of user IDs to assign
notify_allNoNotify all assignees (default false)
start_dateNoStart date as ms timestamp
descriptionNoDescription of the task
custom_fieldsNoCustom field values to set
due_date_timeNoWhether due date includes time
time_estimateNoTime estimate in ms
start_date_timeNoWhether start date includes time
markdown_descriptionNoMarkdown formatted description
check_required_custom_fieldsNoValidate required custom fields
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the obvious action ('Create a new task') and does not disclose side effects, permission needs, idempotency, or failure behavior.

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, grammatically complete sentence with no wasted words. It is front-loaded with the primary action and resource.

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

Completeness1/5

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

For a tool with 18 parameters, no annotations, and no output schema, the description is severely under-specified. It does not mention required fields beyond the schema, return values, or any behavioral nuances, making it inadequate for safe and correct invocation.

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 covers 100% of parameters, so the baseline is 3. The description adds minimal context beyond the schema (the task belongs to a ClickUp list), which aligns with list_id but adds no meaning to the other 17 parameters.

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 verb 'Create' and resource 'task in a ClickUp list' clearly state the tool's core function. It is distinct from siblings like get_task, update_task, and delete_task, and the name differentiates it from create_task_from_template.

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 create_task_from_template or other creation tools. There is no mention of prerequisites, such as the list existing or permission requirements.

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

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