Skip to main content
Glama

update_todo

Idempotent

Update a Planner ToDo by human locator or raw ID, modifying title, markdown description, owner, due date, priority, or visibility.

Instructions

Update a Planner ToDo by human locator or raw todoId. Supports title, markdown description, owner, dueDate including null to clear, priority, and visibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locatorYesLLM-first ToDo locator. Prefer issue/title/owner forms when you do not know the raw Huly ToDo ID.
titleNoa string that will be trimmed
descriptionNoNew ToDo description in markdown. Pass null to clear; empty string is also accepted.
ownerNoa string that will be trimmed
dueDateNoNew due date timestamp, or null to clear.
priorityNoPlanner ToDo priority. Allowed values: no-priority, low, medium, high, urgent.
visibilityNoPlanner ToDo visibility. Allowed values: public, freeBusy, private.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior3/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true. The description adds context about clearing dueDate with null and the locator forms, but does not disclose any significant behavioral traits beyond what annotations and schema provide.

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?

The description is a single sentence that front-loads the key action and capabilities. Every word is functional and there is no wasted text.

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?

The description adequately covers the main updatable fields and the locator forms. Given that an output schema exists, the response format is not needed here. It could mention idempotency or provide more guidance on locator form selection, but overall it is sufficient.

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 description coverage is 100%, and the description adds minimal extra meaning beyond summarizing the field types and null handling. The schema already explains most parameter semantics in detail.

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 clearly states the verb ('Update'), the resource ('Planner ToDo'), and the method of identification ('by human locator or raw todoId'). It also lists the specific fields that can be updated, distinguishing it from sibling tools like create_todo and complete_todo.

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 description implies usage when modifying a todo, but does not explicitly state when to use this tool versus alternatives like create_todo or complete_todo. No when-not or exclusion criteria are provided.

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/dearlordylord/huly-mcp'

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