Skip to main content
Glama

update_subtask

Partially update a subtask to mark it complete, rename it, or change its assignee. Only send the fields you want to change; omitted fields remain unchanged.

Instructions

Partial update of an existing subtask. Returns the updated Subtask.

Only kwargs the caller passes are sent — None means omit, not clear. Use this to mark complete (is_completed=True), rename (name="..."), or change the assignee (assigned_user_id=42). The position field is read-only on this endpoint; use reorder_subtasks to change ordering.

Common 422 (KanbanToolValidationError with parsed field_errors): assigned_user_id not a collaborator on the parent task's board — use list_board_collaborators(board_id) to confirm before retrying.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subtask_idYes
nameNo
is_completedNo
assigned_user_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes
is_completedNo
positionNo
task_idNo
assigned_user_idNo
deleted_atNo
Behavior5/5

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

Adds context beyond annotations: partial update semantics (None means omit), common 422 error with field_errors, and returned object. No contradiction with annotations.

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?

Concise, well-structured sentences with no redundancy. Every sentence adds value and is front-loaded.

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?

With an output schema present, the description appropriately covers usage, parameters, errors, and limitations. No gaps identified.

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?

Adds meaning beyond schema by explaining that None means omit not clear, and mentions that assigned_user_id must be a collaborator. However, not all parameters are explicitly described.

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?

States 'Partial update of an existing subtask' with specific verb and resource, differentiates from siblings like delete_subtask and reorder_subtasks.

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?

Explicit examples of when to use (mark complete, rename, change assignee) and when not to (position is read-only, use reorder_subtasks). Also provides error handling 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