Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_task

Idempotent

Update an existing task's fields: rename, change status, adjust dates, reassign assignees incrementally, and modify priority or description.

Instructions

Update fields on an existing task.

Calls PUT /task/{task_id}. Change the name, description (plain or markdown), status, priority, dates, time estimate, points, parent, or archived flag. Add or remove assignees and group assignees incrementally via the add_assignees / remove_assignees (and group equivalents) lists — ClickUp sends these as {"assignees": {"add": [...], "rem": [...]}}.

When to Use:

  • To edit an existing task or (re)assign people.

When NOT to Use:

  • To create a task — use clickup_create_task.

  • To move a task to a different List — use clickup_move_task.

  • For a single custom-field write, clickup_set_custom_field_value is more reliable than the custom_fields body here.

Returns: A confirmation string naming the task and the fields that changed.

Examples:

  • Reassign: params = {"task_id": "86cxy1", "add_assignees": [123], "remove_assignees": [456]}

  • Retitle + close: params = {"task_id": "86cxy1", "name": "New title", "status": "complete"}

Error Handling: 400 often means an unknown status name; 404 means the task 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 non-readOnly non-destructive idempotent. Description adds that assignees are changed incrementally via add/remove lists, mentions the PUT endpoint, and lists common error codes. No contradiction.

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 sections for usage, returns, examples, and errors. A few extra details but no wasted sentences. Could be slightly more concise but remains clear.

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?

Given the complex input schema, output schema availability, and annotations, the description covers usage guidance, error handling, and key behavioral quirks. Lacks explicit mention of rate limits or authentication, but those are implied by ClickUp context.

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 descriptions for all parameters. Description explains assignee additive behavior beyond schema, points out custom_fields reliability issue, and provides usage examples. Adds value despite not covering every parameter individually.

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 'Update fields on an existing task' and lists specific fields like name, description, status, etc. It distinguishes from sibling tools by explicitly naming when to use create_task, move_task, and set_custom_field_value instead.

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?

Provides explicit 'When to Use' and 'When NOT to Use' sections with clear alternatives: create_task for creation, move_task for moving list, and set_custom_field_value for single custom-field writes.

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