Skip to main content
Glama

Edit a task

taskhold_update
DestructiveIdempotent

Change a task's title, description, priority, project or repeat; only fields you pass change. Status goes through taskhold_start, taskhold_complete, taskhold_block and taskhold_release. Returns the task. Fails on an unknown task_id or project_id (pass project by name).

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": "taskhold_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNew title
repeatNo"every monday at 9am" etc.; "off" stops it; "pause", "resume".
projectNoProject name, e.g. the repo folder ("api-server"). Move it to this project (matched case-insensitively, created on first use).
task_idYesThe ID of the task to update
priorityNoNew priority
project_idNoMove to project by id (null to remove)
descriptionNoNew description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / repeat
      Added value: +{
      +  "description": "\"every monday at 9am\" etc.; \"off\" stops it; \"pause\", \"resume\".",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / project_id / anyOf
      Previous value: -[
      -  {
      -    "format": "uuid",
      -    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "format": "uuid",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / task_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds real context beyond them: partial-update semantics ("only fields you pass change"), the return value, and the two failure conditions. It stops short of saying what the destructive hint actually means in practice (that a passed field overwrites the existing value irreversibly).

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?

Three short sentences, front-loaded with the field scope, then the exclusion routing, then the return and error behavior. No filler and nothing repeated from the schema verbatim.

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?

No output schema exists, but "Returns the task" covers the return contract, and the failure modes plus partial-update rule make the mutation safe to call. Missing is any word on the destructive overwrite of existing field values and on the overlap with taskhold_set_priority, both of which affect correct tool selection.

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 is 3; the description earns an extra point by clarifying the project/project_id split ("pass project by name") and by stating that unspecified fields are left untouched, which the schema does not say. It adds no format or boundary detail beyond that, which is acceptable given the schema's thoroughness.

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?

The description names a specific verb and resource plus the exact mutable field set ("title, description, priority, project or repeat"), and it explicitly carves status changes out to taskhold_start/complete/block/release, so an agent can distinguish it from the mutation siblings without reading schemas.

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?

It gives a clear negative rule (status edits must go through the four named sibling tools) plus a stated precondition failure mode (unknown task_id/project_id). The notable gap is taskhold_set_priority, a sibling that overlaps with this tool's `priority` field, with no guidance on which to prefer.

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