Skip to main content
Glama

Coline

Update a task

update_task
DestructiveIdempotent

Changes a task's title, description, status, priority, dates, labels, assignees or fields. Only the fields given change.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "taskId": "<taskId>"
    },
    "name": "update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
labelsNo
taskIdYesTask id from list_tasks, find_task or get_task.
dueDateNo
priorityNo
statusIdNoStatus id from the board's statuses.
timeZoneNoIANA time zone for the time block.
waitingOnNoWho the task is waiting on; null clears it.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
descriptionNoPlain text; each line becomes a paragraph.
taskboardIdYesBoard id from list_boards.
beforeTaskIdNoPlace it before this task in its status; null puts it last.
parentTaskIdNo
scheduledEndNoEnd of the calendar time block.
assigneeEmailsNoAssign by email instead of id; each must be a workspace member.
scheduledStartNoStart of a calendar time block. Pair with scheduledEnd.
assigneeUserIdsNoWorkspace member ids.
attachmentFileIdsNoImage file ids to show inline in the description.
customFieldValuesNo
descriptionBlocksNoRich description blocks, as Coline's editor stores them.

Output Schema

NameRequiredDescriptionDefault
taskYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered elsewhere. The description's one real contribution is the patch semantics — 'Only the fields given change' — which tells the agent omitted fields are preserved rather than reset. It says nothing about permissions required, whether null clears a value, or side effects such as reordering or assignee notifications.

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 sentences, no redundancy, with the mutability scope stated first and the partial-update rule second. Every clause carries information and nothing needs trimming.

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

Completeness3/5

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

Return values need not be explained because an output schema exists, and annotations cover the destructive/idempotent profile. For a 20-parameter destructive mutation, though, the description leaves structural behaviors (reordering via beforeTaskId, re-parenting, null-clearing, descriptionBlocks vs description) entirely to the schema, which is only 70% documented.

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 70%, so the schema carries most parameter documentation, and the description roughly mirrors it by listing which field groups are updatable. It adds no meaning beyond the schema for notable parameters like beforeTaskId (ordering), parentTaskId (nesting), or waitingOn, and does not flag that timeZone pairs with the scheduled dates.

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 states a specific verb (changes) and resource (a task) and enumerates the mutable field groups: title, description, status, priority, dates, labels, assignees, fields. An agent can immediately tell this is a partial mutation on an existing task. It does not, however, name or distinguish itself from nearby siblings such as create_task, delete_task, or update_task_view.

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?

There is no explicit when/when-not guidance and no named alternative — nothing like 'use create_task to make a task' or 'use update_board for board-level fields'. The only usage-adjacent signal is the implicit assumption that the task already exists, which the agent must infer from the verb 'changes'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources