Skip to main content
Glama

update_task

Edit an existing task's title, notes, deadline, assignees, labels, or checklist while preserving unchanged fields; use add/remove options to modify lists instead of replacing them.

Instructions

Edit a task. Only the arguments you pass change; everything else is sent back exactly as it is (Mizito's save replaces the whole task).

assignees / labels replace the whole list; add_* / remove_* edit it. People and labels accept names or ids. remove_checklist takes item ids or exact titles (see get_task). add_checklist skips titles that already exist. To move columns use move_task; to complete use complete_task.

Mizito has no partial update or version check: a change someone makes in the web app between this tool's read and its save is overwritten.

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": {
      "task_id": "<task_id>"
    },
    "name": "update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
titleNo
labelsNo
task_idYes
deadlineNo
assigneesNo
add_labelsNo
add_assigneesNo
add_checklistNo
remove_labelsNo
clear_deadlineNo
remove_assigneesNo
remove_checklistNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the underlying save model: the whole task is replaced, unsupported fields are sent back unchanged, and there is no partial update or version check, so concurrent web-app edits are overwritten. That lost-update warning and the add_checklist duplicate-skipping behavior are non-obvious traits an agent could not infer from readOnlyHint/destructiveHint/idempotentHint alone.

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?

Front-loads the core behavior, then groups parameter families in one line each, then ends with the sibling routing and the concurrency caveat. Dense but every sentence adds decision-relevant information; nothing is 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?

An output schema exists, so return values need no explanation, and the mutation semantics, duplicates handling, and overwrite risk are all covered for a 13-parameter write tool. The remaining gap is the accepted format for deadline, which an agent must still guess.

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?

With 0% schema description coverage across 13 parameters, the description carries the entire burden and does much of it: replace-vs-add/remove semantics for assignees and labels, names-or-ids acceptance, and that remove_checklist takes item ids or exact titles. Gaps remain: no format for deadline, and title/notes behavior is unstated, though both are largely self-evident from their names.

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 a specific verb and resource ("Edit a task") and immediately qualifies it with the crucial semantic that only passed arguments change. It also names the sibling tools that handle adjacent operations (move_task, complete_task), so an agent can distinguish it without opening any schema.

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 routes two adjacent operations elsewhere: "To move columns use move_task; to complete use complete_task." It also gives the selection rule between two families of parameters (assignees/labels replace vs. add_*/remove_* edit) and points to get_task for checklist item identifiers.

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