Skip to main content
Glama

task_update

Destructive

Edits a task or bug (shared team data); only the passed fields change: title, spec, gist, result, priority, labels, placement (featureID or featureKey, featureID null removes it from the feature; versionID; productID), work iteration, bug fields (build, bugType, stage, browser, devices, fuzzy), type within its kind, modules and components (full new lists), stage assignees and ord. Stage assignees: employee uuid, "any" (any employee) or null (no such stage; the work stage always exists). Status is not changed here; returns link, status, specRevision and changed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "task_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
IDNoTask ID; preferred over key.
keyNoTask number, if the ID is unknown.
ordNoPosition in lists, as drag-and-drop in the web UI; tasks go by ord descending (a feature's tasks follow its plan top down): a value between two neighbours' ord goes between them, above the largest - on top, 0 - last. When neighbours are under 100 apart, the feature's tasks, closed included, are renumbered top down from Date.now() in steps of -10000.
gistNoGist: one or two plain-text sentences "problem → solution", up to 300 characters, without Markdown, links or task keys, in the language of the workspace data; an empty string clears it.
specNoNew spec (requirements): Markdown in the language of the workspace data, HTML is rejected. Replaces the whole field - text, `::: doc` sections and `attach:`, `design:`, `color:` tokens left out are removed.
typeNoNew type: the work type for a task, the criticality for a bug; a task does not become a bug or back.
buildNoBuild where the defect was reproduced (bugs only).
fuzzyNoIntermittent bug: does not reproduce every time (bugs only).
stageNoStand where the bug was reproduced: dev - development and autotests, alpha - manual QA, prod - production data.
titleNoNew name
labelsNoLabels; an empty array removes all.
resultNoReport on the work done: Markdown in the language of the workspace data, HTML is rejected; replaces the whole field, like spec.
browserNoBrowser where the bug was reproduced (bugs only).
bugTypeNoDefect nature (bugs only): ui - interface, fn - functionality, ux - usability, spec - documentation; not the severity, which is type.
devicesNoIDs of devices from the company's QA devices where the bug was reproduced; an unknown ID is rejected. Bugs only; full new list, [] clears it.
priorityNoPriority; a human decision, set only at the user's explicit request.
featureIDNoFeature to move the task to; null removes it from its feature.
moduleIDsNoFull new list of module IDs, replacing the current one; [] removes all.
productIDNoProduct to move the task to; it lands in the product's current development version.
specPatchNoPart of the spec, ops in order: replace / insertBefore / insertAfter / delete a section by heading ("## Chat"; text - whole section), append, find an exact unique fragment → replace. With expectedSpecRevision.
versionIDNoVersion to move the task to when no feature fits.
featureKeyNoKey of the feature to move the task to (#F12), instead of featureID.
resultPatchNoLike specPatch, for result except QA notes; apart from spec.
componentIDsNoFull new list of the actually affected component IDs, replacing the current one; [] removes all, adding means the current ones plus new.
designUnlinkNotrue lets a spec / result write drop design markers (designs left unlinked are deleted); otherwise it is rejected.
testAssigneeNoTester; a bug always keeps its testing stage, null is rejected.
workAssigneeNoAssignee.
workTimePlanNoPlanned work time in minutes, per the assignee's role level
reviewAssigneeNoReviewer.
approvalAssigneeNoApprover.
workIterationDateNoA date within the work iteration, YYYY-MM-DD; moves the work to that iteration.
expectedSpecRevisionNoThe task's current specRevision; required when spec or specPatch changes. A spec with a revision goes in a separate request, with only gist and designUnlink alongside.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "planning",
      -  "analysis",
      -  "design",
      -  "documentation",
      -  "research",
      -  "education",
      -  "other",
      -  "frontend",
      -  "backend",
      -  "fullstack",
      -  "devops",
      -  "tests",
      -  "freetest",
      -  "smoke",
      -  "regression",
      -  "testcase",
      -  "bug_trivial",
      -  "bug_minor",
      -  "bug_major",
      -  "bug_critical",
      -  "bug_block"
      -]New value: +[
      +  "planning",
      +  "analysis",
      +  "design",
      +  "documentation",
      +  "research",
      +  "education",
      +  "marketing",
      +  "other",
      +  "frontend",
      +  "backend",
      +  "fullstack",
      +  "devops",
      +  "tests",
      +  "freetest",
      +  "smoke",
      +  "regression",
      +  "testcase",
      +  "bug_trivial",
      +  "bug_minor",
      +  "bug_major",
      +  "bug_critical",
      +  "bug_block"
      +]
  2. Changed4 schema fields changed
    • changedInput schema / properties / designUnlink / description
      Previous value: -"true lets a spec / result write drop design markers (designs left without links are deleted); otherwise losing a marker is rejected."New value: +"true lets a spec / result write drop design markers (designs left unlinked are deleted); otherwise it is rejected."
    • changedInput schema / properties / expectedSpecRevision / description
      Previous value: -"The task's current specRevision; required when spec changes. A spec with a revision goes in a separate request, with only gist and designUnlink alongside."New value: +"The task's current specRevision; required when spec or specPatch changes. A spec with a revision goes in a separate request, with only gist and designUnlink alongside."
    • addedInput schema / properties / resultPatch
      Added value: +{
      +  "description": "Like specPatch, for result except QA notes; apart from spec.",
      +  "items": {
      +    "properties": {
      +      "find": {
      +        "maxLength": 200000,
      +        "type": "string"
      +      },
      +      "heading": {
      +        "maxLength": 300,
      +        "type": "string"
      +      },
      +      "op": {
      +        "enum": [
      +          "replace",
      +          "insertBefore",
      +          "insertAfter",
      +          "delete",
      +          "append",
      +          "find"
      +        ],
      +        "type": "string"
      +      },
      +      "replace": {
      +        "maxLength": 200000,
      +        "type": "string"
      +      },
      +      "text": {
      +        "maxLength": 200000,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "op"
      +    ],
      +    "type": "object"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
    • addedInput schema / properties / specPatch
      Added value: +{
      +  "description": "Part of the spec, ops in order: replace / insertBefore / insertAfter / delete a section by heading (\"## Chat\"; text - whole section), append, find an exact unique fragment → replace. With expectedSpecRevision.",
      +  "items": {
      +    "properties": {
      +      "find": {
      +        "maxLength": 200000,
      +        "type": "string"
      +      },
      +      "heading": {
      +        "maxLength": 300,
      +        "type": "string"
      +      },
      +      "op": {
      +        "enum": [
      +          "replace",
      +          "insertBefore",
      +          "insertAfter",
      +          "delete",
      +          "append",
      +          "find"
      +        ],
      +        "type": "string"
      +      },
      +      "replace": {
      +        "maxLength": 200000,
      +        "type": "string"
      +      },
      +      "text": {
      +        "maxLength": 200000,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "op"
      +    ],
      +    "type": "object"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
  3. Changed7 schema fields changed
    • changedInput schema / properties / expectedSpecRevision / description
      Previous value: -"The task's current specRevision; required when spec changes."New value: +"The task's current specRevision; required when spec changes. A spec with a revision goes in a separate request, with only gist and designUnlink alongside."
    • addedInput schema / properties / fuzzy
      Added value: +{
      +  "description": "Intermittent bug: does not reproduce every time (bugs only).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / productID
      Added value: +{
      +  "description": "Product to move the task to; it lands in the product's current development version.",
      +  "format": "uuid",
      +  "type": "string"
      +}
    • changedInput schema / properties / testAssignee / description
      Previous value: -"Tester."New value: +"Tester; a bug always keeps its testing stage, null is rejected."
    • changedInput schema / properties / type / description
      Previous value: -"New work type (non-bugs only)."New value: +"New type: the work type for a task, the criticality for a bug; a task does not become a bug or back."
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "planning",
      -  "analysis",
      -  "design",
      -  "documentation",
      -  "research",
      -  "education",
      -  "other",
      -  "frontend",
      -  "backend",
      -  "fullstack",
      -  "devops",
      -  "tests",
      -  "freetest",
      -  "smoke",
      -  "regression",
      -  "testcase"
      -]New value: +[
      +  "planning",
      +  "analysis",
      +  "design",
      +  "documentation",
      +  "research",
      +  "education",
      +  "other",
      +  "frontend",
      +  "backend",
      +  "fullstack",
      +  "devops",
      +  "tests",
      +  "freetest",
      +  "smoke",
      +  "regression",
      +  "testcase",
      +  "bug_trivial",
      +  "bug_minor",
      +  "bug_major",
      +  "bug_critical",
      +  "bug_block"
      +]
    • addedInput schema / properties / workIterationDate
      Added value: +{
      +  "description": "A date within the work iteration, YYYY-MM-DD; moves the work to that iteration.",
      +  "type": "string"
      +}
  4. Changed12 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / approvalAssignee / description
      Previous value: -"Approver: employee uuid, \"any\" (any employee) or null (no approval stage)."New value: +"Approver."
    • changedInput schema / properties / devices / description
      Previous value: -"IDs of devices from the company's QA devices: for a bug - where reproduced, for a task - where to test and where tested. Full new list; [] clears it."New value: +"IDs of devices from the company's QA devices where the bug was reproduced; an unknown ID is rejected. Bugs only; full new list, [] clears it."
    • changedInput schema / properties / featureKey / anyOf
      Previous value: -[
      -  {
      -    "maxLength": 12,
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  {
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "type": "integer"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 12,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "exclusiveMinimum": 0,
      +    "type": "integer"
      +  }
      +]
    • removedInput schema / properties / key / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / key / minimum
      Removed value: --9007199254740991
    • changedInput schema / properties / ord / description
      Previous value: -"Position in lists, as drag-and-drop in the web UI. Tasks are sorted by ord DESCENDING (a feature's tasks follow its plan top down): a value between two neighbors' ord goes between them, above the largest - on top, 0 - last (the server assigns it). When neighbors are under 100 apart or the user asks for a re-sort, all of the feature's tasks including closed ones are renumbered: Date.now() for the top one, then steps of -10000."New value: +"Position in lists, as drag-and-drop in the web UI; tasks go by ord descending (a feature's tasks follow its plan top down): a value between two neighbours' ord goes between them, above the largest - on top, 0 - last. When neighbours are under 100 apart, the feature's tasks, closed included, are renumbered top down from Date.now() in steps of -10000."
    • removedInput schema / properties / ord / maximum
      Removed value: -9007199254740991
    • changedInput schema / properties / reviewAssignee / description
      Previous value: -"Reviewer: employee uuid, \"any\" (any employee) or null (no review stage)."New value: +"Reviewer."
    • changedInput schema / properties / testAssignee / description
      Previous value: -"Tester: employee uuid, \"any\" (any employee) or null (no testing stage)."New value: +"Tester."
    • changedInput schema / properties / workAssignee / description
      Previous value: -"Assignee: employee uuid or \"any\" (any employee); null is not allowed - the work stage always exists."New value: +"Assignee."
    • changedInput schema / properties / workTimePlan / anyOf
      Previous value: -[
      -  {
      -    "maximum": 9007199254740991,
      -    "minimum": -9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  5. Changed1 schema field changed
    • addedInput schema / properties / devices
      Added value: +{
      +  "description": "IDs of devices from the company's QA devices: for a bug - where reproduced, for a task - where to test and where tested. Full new list; [] clears it.",
      +  "items": {
      +    "format": "uuid",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  6. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only flag destructiveHint=true; the description goes well past them by spelling out what gets destroyed: spec/result "replaces the whole field" dropping ::: doc sections and attach:/design:/color: tokens, empty arrays clearing labels/modules/components, featureID null detaching from the feature, designUnlink deleting unlinked designs, and unknown device IDs being rejected. It also discloses the return payload (link, status, specRevision, changed) and the stage-assignee sentinel values.

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?

A single dense sentence with nested parentheses — heavy but efficient for 32 parameters, with the core partial-update rule and the status exclusion front-loaded. Some clauses (e.g., 'modules and components (full new lists)') restate schema text and could be dropped.

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 a 32-parameter destructive mutation with no output schema, the description covers side effects, replacement semantics, optimistic-concurrency requirements, sentinel values, and return fields. The remaining gap is routing guidance for the status/assignment-change siblings.

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?

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning on top: it groups placement fields, clarifies "full new lists" semantics for modules/components, and documents stage-assignee values ("employee uuid, 'any', or null") that the schema text does not cover for testAssignee/reviewAssignee/approvalAssignee.

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?

Specific verb+resource ("Edits a task or bug") plus the key partial-update rule "only the passed fields change". It also carves out status changes ("Status is not changed here"), which implicitly separates it from task_done/task_take, though it never names those siblings explicitly.

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?

Usable context is embedded throughout: priority "set only at the user's explicit request", expectedSpecRevision "required when spec or specPatch changes", and the concurrency rule that a spec-with-revision "goes in a separate request, with only gist and designUnlink alongside". Missing is an explicit pointer to the sibling to use for status transitions.

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