Skip to main content
Glama
lucaspsantana

clickup-custom-mcp

clickup_update_task

Update any ClickUp task by providing its ID and modifying fields like name, description, status, priority, due date, and assignees.

Instructions

Update a ClickUp task by task_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesClickUp task ID
nameNo
descriptionNo
statusNoStatus name in the list
priorityNo1=urgent, 2=high, 3=normal, 4=low
due_dateNoUnix timestamp in milliseconds
assignees_addNoUser IDs to add as assignees
assignees_remNoUser IDs to remove from assignees
Behavior2/5

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

With no annotations, the description carries the full burden. It does not disclose whether updates are partial or full, required permissions, side effects, or rate limits. The single sentence is insufficient for a mutation tool.

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?

Extremely concise at one sentence with no wasted words. However, it could benefit from slight expansion without losing efficiency.

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

Completeness2/5

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

Given 8 parameters and no output schema, the description is incomplete. It fails to explain partial update behavior, return value, or error scenarios.

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 high (75%). The description adds no additional meaning beyond the schema, but that is acceptable per guidelines (baseline 3).

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 clearly states the action 'Update' and the resource 'ClickUp task' with identifier 'task_id'. It is specific but does not elaborate on what can be updated, leaving some ambiguity.

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 guidance is provided on when to use this tool versus siblings like clickup_list_tasks. There are no when-to-use or when-not-to-use instructions.

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

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