Skip to main content
Glama

update_task

Modify existing task details like description, priority, due dates, and tags while automatically assigning it to the requesting agent for exclusive editing.

Instructions

Update fields on an existing task. Auto-claims the task for the calling agent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask ID or UUID
agent_idYesGlobally unique agent identifier (e.g. "claude-opus-<uuid>"). Each agent instance MUST use a distinct ID to prevent collisions between parallel agents.
descriptionNoNew description
projectNoNew project
priorityNoPriority: H, M, or L
tagsYesTags to add
remove_tagsYesTags to remove
dueNoDate in any format Taskwarrior accepts (e.g. 2024-12-25, tomorrow, eow)
scheduledNoDate in any format Taskwarrior accepts (e.g. 2024-12-25, tomorrow, eow)
waitNoDate in any format Taskwarrior accepts (e.g. 2024-12-25, tomorrow, eow)
untilNoDate in any format Taskwarrior accepts (e.g. 2024-12-25, tomorrow, eow)
dependsYesUUIDs this task depends on

Implementation Reference

  • The `modifyTask` function executes the actual task modification by building arguments and running the 'task' CLI command.
    export async function modifyTask(id: string, fields: TaskFields, agentId: string): Promise<void> {
      const uuid = await ensureClaim(id, agentId);
      try {
        const args = buildModifyArgs(fields);
        await runCommand('task', [uuid, 'modify', ...args]);
      } catch (err) {
        throw new Error(`Failed to modify task ${id}: ${(err as Error).message}`);
      }
    }
  • src/index.ts:138-170 (registration)
    Registration of the 'update_task' tool including input schema definition and call to modifyTask handler.
    server.tool(
      'update_task',
      'Update fields on an existing task. Auto-claims the task for the calling agent.',
      {
        id: idParam,
        agent_id: agentIdParam,
        description: z.string().optional().describe('New description'),
        project: z.string().optional().describe('New project'),
        priority: priorityParam,
        tags: tagsParam,
        remove_tags: z.preprocess(coerceStringArray, z.array(z.string()).optional()).describe('Tags to remove'),
        due: dateParam,
        scheduled: dateParam,
        wait: dateParam,
        until: dateParam,
        depends: z.preprocess(coerceStringArray, z.array(z.string()).optional()).describe('UUIDs this task depends on'),
      },
      async ({ id, agent_id, remove_tags, ...fields }) => {
        try {
          await modifyTask(id, {
            description: fields.description,
            project: fields.project,
            priority: fields.priority as Priority | undefined,
            tags: fields.tags,
            removeTags: remove_tags,
            due: fields.due,
            scheduled: fields.scheduled,
            wait: fields.wait,
            until: fields.until,
            depends: fields.depends,
          }, agent_id);
          return { content: [{ type: 'text', text: `Task ${id} updated.` }] };
        } catch (err) {
Behavior3/5

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

No annotations provided, so description carries full burden. It successfully discloses the side effect of auto-claiming, but omits other critical behavioral details like error handling (task not found), idempotency, or whether partial updates are supported.

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, zero waste. Front-loaded with the core operation, followed immediately by the critical side effect. Every word earns its place.

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?

Adequate for basic invocation but incomplete for a 12-parameter mutation tool lacking annotations and output schema. Missing explanation of auto-claim mechanics, the interaction between tags/remove_tags, and error scenarios.

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 has 100% description coverage, establishing baseline 3. The description adds minimal value beyond the schema—mentioning 'fields' generically without clarifying the unusual requirement that tags, remove_tags, and depends are mandatory (requiring empty arrays for no-op).

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?

Clear verb ('Update') and resource ('existing task') with specific scope. The 'auto-claims' behavior distinguishes it from sibling tools like annotate_task or complete_task, though it could clarify what 'fields' entails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The auto-claim behavior provides implicit guidance (use this when taking ownership), but lacks explicit when-to-use comparisons against siblings like create_task or annotate_task, and doesn't warn about the required array parameters.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/maxronner/taskwarrior-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server