Skip to main content
Glama

update_task

Update any field of a task by specifying only the fields to change. Supports modifying status, priority, due date, assignees, custom fields, and more.

Instructions

Update any field of a task. Pass only the fields you want to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask ID.
nameNo
descriptionNoPlain-text description.
markdown_contentNoMarkdown description (overrides description).
statusNo
priorityNo1=urgent .. 4=low, null clears.
due_dateNoDate as ISO string, epoch ms, or relative ("tomorrow", "in 3 days", "+2h").
due_date_timeNo
start_dateNoDate as ISO string, epoch ms, or relative ("tomorrow", "in 3 days", "+2h").
start_date_timeNo
time_estimateNoEstimate in milliseconds.
assigneesNoFull set of assignee user ids. On update this REPLACES the current assignees (use assignees_add/assignees_rem for incremental changes).
tagsNo
parentNoParent task id (makes this a subtask).
custom_fieldsNoArray of { id, value } custom field assignments.
custom_item_idNoCustom task type id.
archivedNo
assignees_addNoAssignees to add (incremental).
assignees_remNoAssignees to remove (incremental).
custom_task_idsNoTreat task_id as a custom id (requires team_id).
team_idNoTeam/Workspace ID. Falls back to CLICKUP_TEAM_ID when omitted.
Behavior2/5

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

No annotations provided; description only indicates general update behavior. Lacks details on destructive potential, authentication requirements, rate limits, or error handling. Schema descriptions fill some gaps, but overall behavioral context is minimal.

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?

Two short, front-loaded sentences with no redundancy. Every word adds value: 'Update any field' and 'Pass only the fields you want to change'.

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?

For a complex tool with 21 parameters and no output schema, the description lacks completeness. Missing details on idempotency, error responses, permission requirements, and relation to similar update tools.

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 71%, with many parameters described in schema. The description adds the partial-update pattern but no additional semantic depth beyond schema. Baseline 3 is appropriate.

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?

Description clearly states 'Update any field of a task', specifying the verb and resource. It distinguishes from siblings like create_task, delete_task, and update_bulk_tasks by focusing on any-field partial updates.

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?

Provides guidance to pass only changed fields, but does not explicitly differentiate from related tools like update_bulk_tasks or state when not to use this tool. Lacks exclusion or alternative references.

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

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