Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_task

Create a task in a ClickUp List with assignees, tags, priority, due dates, markdown description, subtask links, and custom fields. Specify the List ID and task name to add a new task.

Instructions

Create a task inside a List.

Calls POST /list/{list_id}/task. Supports the full create surface: assignees and group assignees, tags, status, priority, due/start dates (unix ms), time estimate, sprint points, a markdown or plain description, custom-field values, subtask creation via parent, and a custom task type via custom_item_id.

When to Use:

  • To add a new task (or a subtask, by setting parent) to a known List.

When NOT to Use:

  • To change an existing task — use clickup_update_task.

  • To copy a predefined template — use clickup_create_task_from_template.

Returns: A confirmation string with the new task's name, id, and URL.

Examples:

  • Minimal: params = {"list_id": "901", "name": "Draft spec"}

  • Rich: params = {"list_id": "901", "name": "Ship v2", "markdown_content": "## Goal\n...", "assignees": [123], "priority": 2, "due_date": 1735689600000, "due_date_time": true, "tags": ["release"], "custom_fields": [{"id": "abc", "value": "done"}]}

Error Handling: 400 usually means an unknown status/tag or a malformed custom_fields entry; 404 means the List id is wrong.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds detail about what is created (task or subtask), the return format (confirmation string), and error conditions. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections. Slightly verbose but every sentence adds value. Examples and error handling are helpful.

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?

Comprehensive: covers all major features (subtasks, custom fields, markdown, etc.), includes return format, examples, and error handling. Given the output schema exists, the description is complete.

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?

Despite the schema having parameter descriptions, the context signals indicate 0% coverage. The description compensates with a summary of supported parameters (assignees, tags, custom fields etc.) and rich examples that demonstrate usage patterns.

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?

Clearly states 'Create a task inside a List' with a specific verb and resource. Distinguishes from siblings like clickup_update_task and clickup_create_task_from_template in the 'When NOT to Use' section.

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

Usage Guidelines5/5

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

Explicit 'When to Use' and 'When NOT to Use' sections provide clear guidance. Also includes error handling advice (400/404) which helps the agent diagnose failures.

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

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