Skip to main content
Glama

update_task

Update an existing task's status, title, owner, notes, due date, or recurrence. Only specified fields are changed; marking a recurring task done creates its next occurrence.

Instructions

Update an existing task — its status, title, owner, notes, due date, or recurrence.

The companion to create_task and get_tasks: use this to mark a task done or
blocked, reschedule it, reassign it, or edit its details. Only the fields you
pass are changed; empty arguments leave the existing value untouched. Marking
a recurring task "done" automatically creates its next occurrence. Find a
task_id with get_tasks; use delete_task to remove a task entirely.

Args:
    task_id: ID of the task to update (as shown by get_tasks). Required.
    status: New status — "open", "done", or "blocked". Empty = unchanged.
    title: New title. Empty = unchanged.
    owner: New owner. Empty = unchanged.
    notes: New notes/details. Empty = unchanged.
    due_date: New due date in "YYYY-MM-DD" format. Empty = unchanged.
    recurrence: New repeat — "daily", "weekly", "monthly", or "yearly".
        Empty = unchanged; pass "none" to clear an existing recurrence.

Returns:
    A confirmation listing the changed fields (and the next-occurrence id if a
    recurring task was completed), or a note if the task_id was not found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
statusNo
titleNo
ownerNo
notesNo
due_dateNo
recurrenceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses key behaviors: partial updates (only passed fields changed), empty args leave unchanged, automatic creation of next occurrence for recurring tasks on completion, and return format (confirmation or not-found note). No annotations provided, so description fully addresses transparency.

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?

Very concise—two short paragraphs plus bullet-style Args and Returns. Each sentence adds value without redundancy. Front-loaded with purpose, then details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all necessary aspects: input parameters, behavioral nuances, return value. Despite no annotations and 7 parameters, the description is complete and aligns with the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so description must detail each parameter. It does so comprehensively: task_id as required, status with allowed values, title/owner/notes as free text, due_date with format, recurrence with options and special value 'none' to clear. Adds meaning beyond schema structure.

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?

Clearly states it updates an existing task with specific fields (status, title, owner, etc.), and distinguishes itself from siblings create_task, get_tasks, and delete_task.

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 describes when to use (companion to create_task and get_tasks), what it does (mark done, reschedule, reassign), and what not to use it for (removal, use delete_task). Provides context for recurring task behavior.

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/SVerITG/Metis'

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