Skip to main content
Glama

clickup_create_task

Create a new task in a ClickUp list with customizable details such as description, priority, assignees, and due dates.

Instructions

Create a new task in a list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesClickUp list ID
nameYesTask name
descriptionNoTask description (plain text or markdown)
markdown_descriptionNoTask description in markdown
statusNoStatus name (must match list's statuses)
priorityNoPriority: 1=urgent, 2=high, 3=normal, 4=low
assigneesNoArray of user IDs to assign
tagsNoArray of tag names
due_dateNoDue date as Unix timestamp in milliseconds
due_date_timeNoWhether due_date includes time
start_dateNoStart date as Unix timestamp in milliseconds
start_date_timeNoWhether start_date includes time
time_estimateNoTime estimate in milliseconds
parentNoParent task ID (to create subtask)
notify_allNoNotify assignees (default true)
custom_fieldsNoCustom field values to set
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the basic function without mentioning side effects, idempotency, permissions, rate limits, or error handling. This is insufficient for informed agent decision-making.

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 extremely concise and front-loaded, conveying the essential purpose in just six words. Every word is necessary and contributes directly to understanding. No wasted text.

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?

Given the tool's complexity (16 parameters, no annotations, no output schema), the description is severely incomplete. It omits return values, error scenarios, behavioral nuances, and integration context with sibling tools. A more comprehensive description is needed.

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 input schema has 100% description coverage, so the schema itself documents all parameter meanings. The description adds no additional semantic value or contextual hints beyond the schema. Score remains at baseline 3.

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 'Create a new task in a list' clearly states the action (create), the resource (task), and the scope (in a list). It effectively distinguishes this from sibling tools like clickup_update_task or clickup_delete_task.

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 usage guidelines are provided. The description does not mention when to use this tool versus alternatives (e.g., clickup_update_task), nor does it specify prerequisites or contexts that might influence selection.

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/cvrt-jh/clickup-mcp'

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