Skip to main content
Glama

update_task

Update an existing task by setting new values for title, notes, completion, dates, or effort. Only specified fields are modified.

Instructions

Update an existing task. Only provided fields are changed.

Args: task_id: The uniqueID of the task. title: New title. note: New note text. completed: True to mark complete, False to mark incomplete. manual_start_date: ISO date string, or empty string to clear. manual_end_date: ISO date string, or empty string to clear. effort_seconds: Total effort in person-seconds. Pass 0 to set to zero; None (omit) to leave unchanged. min_effort_seconds: Three-point estimation minimum (person-seconds). expected_effort_seconds: Three-point estimation expected value. max_effort_seconds: Three-point estimation maximum. start_no_earlier_than: ISO date string, or empty string to clear. Maps to task.startNoEarlierThanDate. start_no_later_than: ISO date string, or empty string to clear. Maps to task.startNoLaterThanDate. end_no_earlier_than: ISO date string, or empty string to clear. Maps to task.endNoEarlierThanDate. end_no_later_than: ISO date string, or empty string to clear. Maps to task.endNoLaterThanDate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
titleNo
noteNo
completedNo
manual_start_dateNo
manual_end_dateNo
effort_secondsNo
min_effort_secondsNo
expected_effort_secondsNo
max_effort_secondsNo
start_no_earlier_thanNo
start_no_later_thanNo
end_no_earlier_thanNo
end_no_later_thanNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Despite no annotations, the description discloses key behavioral traits: it confirms mutation ('Update'), explains partial update semantics ('Only provided fields are changed'), and details parameter-specific behaviors like clearing dates with empty strings and leaving fields unchanged with null omission. However, it does not mention error handling or idempotency.

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?

The description is efficiently front-loaded with the core purpose, then lists parameters in a clear, readable format. While it is lengthy due to 14 parameters, every line adds value without redundancy. A slightly more structured list format could improve scannability.

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?

Given the tool's complexity (14 parameters), the description covers all input semantics thoroughly. The presence of an output schema absolves the need to describe return values. The description could be improved by mentioning behavior for non-existent task_id or other error scenarios.

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?

With 0% schema coverage, the description fully compensates by detailing each parameter's purpose, format (ISO dates), units (person-seconds), and special values (0 to set, None to omit). It also clarifies internal field mappings for date constraints. This goes well beyond the schema's minimal type info.

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?

Description clearly states 'Update an existing task' with a specific verb and resource, and adds the important qualifier 'Only provided fields are changed' to distinguish from full replacement. This is distinct from sibling tools like create_task 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 Guidelines3/5

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

Description implies use for updating existing tasks but provides no explicit guidance on when to use this tool vs alternatives (e.g., move_task, assign_resource). No preconditions or when-not-to-use advice is given.

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/johntrandall/omniplan-mcp'

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