Skip to main content
Glama

Update task

update_task
Destructive

Update supplied task fields: name, status, priority, assignees and dates. Resolve the target, status and members first. assigneeIds replaces the entire list; [] unassigns everyone. Null clears dates or priority. Use edit_task_content for the description. Preserve requestId on retries.

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

Input Schema

NameRequiredDescriptionDefault
idYesExisting target ID returned by the matching list, read or search tool. Preserve any search type prefix. Do not invent IDs.
nameNoThe name requested by the user. For updates, omit to keep the current name.
deadlineNoISO 8601 deadline including a timezone offset. Omit to leave unchanged; null clears the deadline.
priorityNoPriority: 0 Low, 1 Normal, 2 High, 3 Urgent. For updates, null clears it.
requestIdYesA unique UUID for this intended action. Reuse it unchanged when retrying the same action.
startDateNoISO 8601 start date with timezone. Omit to preserve; null clears it.
assigneeIdsNoFull replacement list of existing project member IDs from list_project_members. [] unassigns everyone; omit to preserve.
stateProjectIdNoTask status ID from list_project_statuses for the destination project.

Output Schema

NameRequiredDescriptionDefault
taskYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / assigneeIds
      Added value: +{
      +  "description": "Full replacement list of existing project member IDs from list_project_members. [] unassigns everyone; omit to preserve.",
      +  "items": {
      +    "maxLength": 100,
      +    "minLength": 1,
      +    "pattern": "^[A-Za-z0-9_-]+$",
      +    "type": "string"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
    • changedInput schema / properties / id / description
      Previous value: -"Existing task ID returned by list_tasks or search. Do not invent IDs."New value: +"Existing target ID returned by the matching list, read or search tool. Preserve any search type prefix. Do not invent IDs."
    • addedInput schema / properties / priority
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 3,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Priority: 0 Low, 1 Normal, 2 High, 3 Urgent. For updates, null clears it."
      +}
    • addedInput schema / properties / startDate
      Added value: +{
      +  "anyOf": [
      +    {
      +      "format": "date-time",
      +      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "ISO 8601 start date with timezone. Omit to preserve; null clears it."
      +}
    • addedInput schema / properties / stateProjectId
      Added value: +{
      +  "description": "Task status ID from list_project_statuses for the destination project.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "pattern": "^[A-Za-z0-9_-]+$",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the annotations by spelling out the exact destructive semantics: assigneeIds is a full replacement and [] unassigns everyone, and null clears dates or priority while omission preserves. This is precisely the 'what gets destroyed' context that matters for a destructiveHint=true, idempotentHint=false tool. It does not mention permission/auth requirements, and the retry/requestId note partially overlaps what the schema already explains.

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?

Five short clauses, front-loaded with the mutated field list, then prerequisites, then the risky replacement/null semantics, then the sibling hand-off and retry rule. Every sentence carries distinct information with no filler.

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?

For an 8-parameter mutation tool with full schema coverage, an output schema, and destructive/idempotency annotations, the description covers the semantics an agent could most easily get wrong (list replacement, null-clearing, retry identity). It stops short of describing effects of status moves (stateProjectId from a destination project's statuses) or resulting side effects on assignees.

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 100%, so every parameter (including the omit-vs-null vs [] semantics) is already documented in the schema. The description restates the assigneeIds replacement and null-clearing rules without adding syntax or constraints beyond them. Baseline 3 is correct when the schema does the heavy lifting.

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 plus the exact fields it mutates (name, status, priority, assignees, dates), and explicitly carves out the description field to a named sibling (edit_task_content). An agent can distinguish it from update_doc, create_task and edit_task_content 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 Guidelines4/5

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

'Resolve the target, status and members first' gives an explicit prerequisite ordering, and 'Use edit_task_content for the description' names the alternative for a field this tool does not handle. It also gives retry guidance ('Preserve requestId on retries'). No explicit when-not-to-use statement beyond the description pointer, so not a full 5.

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.