Skip to main content
Glama

Update task

update_task
Idempotent

Modify any field of an existing task—title, status, priority, assignees, tags, due date, description. Pass only fields to change; returns the updated task.

Instructions

Update one or more fields of an existing task. Pass only the fields you want to change — all are optional. Returns the updated task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask UUID to update
titleNoNew title
statusNoNew status. Default values: OPEN, IN_PROGRESS, IN_REVIEW, NEEDS_INFO, DONE (= "Closed - done"), CLOSED (= "Closed - won't do"). Use NEEDS_INFO when the task is blocked waiting for clarification. A board may define custom statuses — read board.config.statuses from get_board.
tag_idsNoReplace the whole tag list with these tag IDs (empty array clears all tags)
due_dateNoNew due date as ISO string, or null to clear
priorityNoNew priority, low to high: MINOR, ORDINARY ("Low"), MEDIUM, IMPORTANT ("High"), BLOCKER. A board may define custom priorities — read board.config.priorities from get_board.
stage_idNoAssign to this stage ID, or null to remove (use get_board to see stages)
column_idNoMove to this kanban column ID (use list_board_columns to get IDs)
parent_idNoSet parent task UUID, or null to make top-level
tag_namesNoReplace the whole tag list with these names (empty array clears all tags). Names are found on the board or created there. Max 10 per task.
descriptionNoNew description (markdown supported)
watcher_idsNoReplace full watcher list with these user UUIDs
assignee_idsNoReplace full assignee list with these user UUIDs
original_estimate_minutesNoTime estimate in minutes
Behavior4/5

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

The description adds partial-update semantics ('pass only the fields you want to change') and states the return value, which is not visible from annotations. Annotations already cover read-only/destructive/idempotence, so no contradiction; some additional detail on side effects could push it higher.

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?

Three short sentences, front-loaded with the action, and every word adds value. No repetition of schema details or padding.

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?

With 14 richly documented parameters and no output schema, the description correctly focuses on partial update behavior and return value. It stops short of explicitly noting the required id and error conditions, but these are inferable or present in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, the description provides the key global instruction that only supplied fields are updated and all are optional, which is not explicitly stated in the schema. This materially reduces the risk of sending a full replacement payload.

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 uses a specific verb and resource ('Update... an existing task') and clarifies the scope ('one or more fields'), distinguishing it from create/delete/comment-update siblings. The return value is also stated, removing ambiguity.

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

Usage Guidelines4/5

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

It clearly conveys when to use it: modifying an existing task with selective fields. It does not name alternatives or exclusions, but the context is unambiguous and the sibling tools are easily differentiated by task vs. comment/board operations.

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/gonnagetapower/kelvia-mcp'

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