Skip to main content
Glama
helbertparanhos

clickup-mcp-pro

by helbertparanhos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_task

Create a task in a ClickUp List with specified details like description, status, priority, dates, assignees, tags, custom fields, and parent for subtasks. Returns the created task ID.

Instructions

Create a new task in a List, setting any fields you provide (description, status, priority, dates, assignees, tags, custom fields, parent for subtasks). Returns the created task with its id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesID of the List to create the task in.
nameYesName/title of the new task.
descriptionNoPlain-text task description.
markdown_contentNoMarkdown task description. Takes precedence over `description` if both are given.
statusNoStatus name (must exist in the task's List, e.g. 'to do', 'in progress', 'complete').
priorityNoPriority: 1=urgent, 2=high, 3=normal, 4=low; null clears it.
due_dateNoDue date (natural language, ISO, or epoch ms).
due_date_timeNoIf true, the due date includes a specific time of day.
start_dateNoStart date (natural language, ISO, or epoch ms).
start_date_timeNoIf true, the start date includes a specific time of day.
time_estimateNoTime estimate in milliseconds.
assigneesNoFull set of assignee user ids. On update this REPLACES the current assignees (use assignees_add/assignees_rem for incremental changes).
tagsNoTag names to set on the task (must already exist in the Space).
parentNoParent task id; set to make this task a subtask of that parent.
custom_fieldsNoArray of custom field assignments as { id, value } objects.
custom_item_idNoCustom task type id (from `get_custom_task_types`); null for the default Task type.
custom_task_idsNoSet true to treat `task_id` as a custom task ID instead of a native ClickUp ID. Requires `team_id`.
team_idNoTeam/Workspace ID. Falls back to CLICKUP_TEAM_ID when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changedv1.0.1
    • changedInput schema / properties / custom_fields / description
      Previous value: -"Array of { id, value } custom field assignments."New value: +"Array of custom field assignments as { id, value } objects."
    • addedInput schema / properties / custom_fields / items / properties / id / description
      Added value: +"Custom field id."
    • addedInput schema / properties / custom_fields / items / properties / value / description
      Added value: +"Value in the shape required by the field's type."
    • changedInput schema / properties / custom_item_id / description
      Previous value: -"Custom task type id."New value: +"Custom task type id (from `get_custom_task_types`); null for the default Task type."
    • changedInput schema / properties / custom_task_ids / description
      Previous value: -"Treat task_id as a custom id (requires team_id)."New value: +"Set true to treat `task_id` as a custom task ID instead of a native ClickUp ID. Requires `team_id`."
    • changedInput schema / properties / description / description
      Previous value: -"Plain-text description."New value: +"Plain-text task description."
    • changedInput schema / properties / due_date / description
      Previous value: -"Date as ISO string, epoch ms, or relative (\"tomorrow\", \"in 3 days\", \"+2h\")."New value: +"Due date (natural language, ISO, or epoch ms)."
    • addedInput schema / properties / due_date_time / description
      Added value: +"If true, the due date includes a specific time of day."
    • changedInput schema / properties / list_id / description
      Previous value: -"List ID."New value: +"ID of the List to create the task in."
    • changedInput schema / properties / markdown_content / description
      Previous value: -"Markdown description (overrides description)."New value: +"Markdown task description. Takes precedence over `description` if both are given."
    • addedInput schema / properties / name / description
      Added value: +"Name/title of the new task."
    • changedInput schema / properties / parent / description
      Previous value: -"Parent task id (makes this a subtask)."New value: +"Parent task id; set to make this task a subtask of that parent."
    • changedInput schema / properties / priority / description
      Previous value: -"1=urgent .. 4=low, null clears."New value: +"Priority: 1=urgent, 2=high, 3=normal, 4=low; null clears it."
    • changedInput schema / properties / start_date / description
      Previous value: -"Date as ISO string, epoch ms, or relative (\"tomorrow\", \"in 3 days\", \"+2h\")."New value: +"Start date (natural language, ISO, or epoch ms)."
    • addedInput schema / properties / start_date_time / description
      Added value: +"If true, the start date includes a specific time of day."
    • addedInput schema / properties / status / description
      Added value: +"Status name (must exist in the task's List, e.g. 'to do', 'in progress', 'complete')."
    • addedInput schema / properties / tags / description
      Added value: +"Tag names to set on the task (must already exist in the Space)."
    • changedInput schema / properties / time_estimate / description
      Previous value: -"Estimate in milliseconds."New value: +"Time estimate in milliseconds."
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

The description clarifies it is a mutation (creates a task) and returns the created object with its ID. However, it does not disclose side effects like notifications, rate limits, or dependencies. Given no annotations, more behavioral context would be helpful.

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 two sentences, front-loaded with the main action, and contains no redundant information. Every word earns its place.

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

Completeness4/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 and no output schema, the description covers the purpose, fields, and return value. It omits some nuances (e.g., markdown_content precedence over description) but is largely sufficient for selection and 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?

Schema coverage is 100%, so the description adds little beyond listing field categories (e.g., 'parent for subtasks'). The schema already describes each parameter in detail, so the description meets the baseline but does not enhance semantics significantly.

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 a List' with a specific verb and resource. It lists the settable fields, distinguishing it from siblings like update_task, create_bulk_tasks, and create_checklist.

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 implicitly indicates when to use (creating a single task) but does not explicitly state when not to use it (e.g., use update_task for modifications, create_bulk_tasks for multiple). No exclusions or alternatives are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools