Skip to main content
Glama

update_task

Update specific fields of a Kanban Tool task—name, priority, due date, assignee, or tags—without altering other fields. Only provided values are sent; null fields are omitted.

Instructions

Partially update a task's fields. Only the kwargs you pass are sent; None means omit, not clear (the API ignores nulls, doesn't wipe).

Field set mirrors create_task; same wire conventions for priority, tags, and date fields. assigned_user_id sets the single assignee — Kanban Tool tasks have one assignee, not a list. For column/lane/position changes prefer move_task — it's the intent-revealing surface for that workflow.

Raises ValueError if every field is None (no-op guard).

Common 422s (KanbanToolValidationError with parsed field_errors): lane_id from a different board → use get_board(board_id).columns on the destination board first; assigned_user_id not a board collaborator → list_board_collaborators(board_id) to confirm.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
nameNo
descriptionNo
board_idNo
lane_idNo
swimlane_idNo
positionNo
priorityNo
colorNo
due_dateNo
start_dateNo
tagsNo
assigned_user_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes
descriptionNo
board_idNo
workflow_stage_idNo
swimlane_idNo
positionNo
priorityNo
colorNo
due_dateNo
start_dateNo
tagsNo
assigned_user_idNo
archived_atNo
block_reasonNo
subtasks_countNo
subtasksNo
comments_countNo
timers_totalNo
time_trackersNo
created_atNo
updated_atNo
size_estimateNo
size_estimate_descriptionNo
time_estimateNo
search_tagsNo
card_colorNo
card_color_in_rgbNo
card_color_invertNo
card_type_idNo
recurring_scheduleNo
reminders_scheduleNo
linked_tasksNo
linked_tasks_statusNo
task_dependenciesNo
collaboratorsNo
attachmentsNo
attachments_countNo
created_by_idNo
moved_atNo
postponed_untilNo
subtasks_completed_countNo
external_idNo
external_linkNo
custom_fieldsNo
is_archivedYesTrue iff the task has an archival timestamp.
is_blockedYesTrue iff the task has a non-empty block reason.
Behavior5/5

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

Describes behavior beyond annotations: null means omit not clear, ValueError for no-op, common validation errors. No contradiction with annotations (destructiveHint=false, readOnlyHint=false).

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 well-structured with paragraphs and bullet points, front-loaded with core purpose. It is slightly lengthy but remains clear and organized.

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

Completeness5/5

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

Given 13 parameters and 0% schema description coverage, the description adequately explains semantics, error handling, sibling tool relationships, and common issues. Output schema exists but not needed for completeness.

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?

Although schema coverage is 0%, the description adds meaning for key parameters like assigned_user_id and references conventions for priority, tags, date fields. It doesn't cover all 13 parameters individually but provides enough context.

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 'Partially update a task's fields' and specifies that only passed kwargs are sent. It distinguishes from move_task and create_task, showing unique purpose.

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?

Explicitly states when to prefer move_task for column/lane/position changes. Warns about common 422 errors and directs to use get_board and list_board_collaborators. Provides clear when-not-to-use guidance.

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/VeryLongOrgNameSuchWow/kanbantool-mcp'

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