Skip to main content
Glama
rafadepaula

@rafadepaula/clickup-mcp

by rafadepaula
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

clickup_update_task

Update ClickUp task properties such as status, priority, dates, assignees, custom fields, and task type by supplying a task ID and the fields to change.

Instructions

Update task properties. Requires task_id and at least one field to change. Supports assignees (user IDs, emails, usernames, or "me"), custom fields as [{id, value}], and task_type by name (or 'none' to reset).

Input Schema

NameRequiredDescriptionDefault
nameNo
statusNoNew status (must be valid for the task's list).
task_idYesTask ID (supports custom IDs like 'DEV-1234')
due_dateNoYYYY-MM-DD or YYYY-MM-DD HH:MM format. Pass 'none' to clear. Omit to leave unchanged.
priorityNoSet priority, or 'none' to clear. Omit to leave unchanged.
assigneesNoArray of assignee user IDs. Use clickup_resolve_assignees to convert emails, usernames, or "me" to user IDs if needed.
task_typeNoTo change the task type, pass the type name as a string (e.g., 'Bug', 'Feature', 'Milestone'). The type must exist in the workspace. To revert to the default 'Task' type, pass 'none'. Omit entirely to leave unchanged.
start_dateNoYYYY-MM-DD or YYYY-MM-DD HH:MM format. Pass 'none' to clear. Omit to leave unchanged.
workspace_idNoWorkspace ID (digits only). Only needed when you have multiple workspaces.
custom_fieldsNoArray of custom field values to set on the task. Each object must have an 'id' and 'value' property.
time_estimateNoTime estimate in minutes (e.g., '150' for 2h 30m).
markdown_descriptionNoTask description in markdown format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It identifies this as a mutation and mentions reset semantics for task_type, but it omits permissions, side effects, reversibility, and what the response contains.

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?

The description is three efficient sentences and front-loads the core action and precondition. There is little waste, though the supported-field sentence is somewhat dense.

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

Completeness3/5

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

The rich input schema covers most parameter details, and the description covers the core update semantics and a few special fields. Still, for a 12-parameter mutation tool with no annotations and no output schema, it should say more about permissions, side effects, or response behavior.

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 description coverage is 92%, so the schema already documents nearly all parameters in detail. The description adds a little context about assignee formats, custom field shape, and task_type reset behavior, but much of this repeats or lightly extends the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: 'Update task properties.' It is distinguishable from create/delete/move siblings, but it does not explicitly name or contrast against them.

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

Usage Guidelines3/5

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

It gives a useful precondition ('Requires task_id and at least one field to change'), which clarifies when the tool is callable. However, it does not explain when to use this versus alternatives like clickup_move_task, clickup_add_tag_to_task, or clickup_create_task.

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