Skip to main content
Glama

doer_update_todo_list

Update an existing todo list's title, Markdown body, project assignment, or pin state in Doer, including reordering pinned items and optionally returning rendered HTML.

Instructions

Update an existing todo list's title, markdown body, project assignment, or pin state in Doer

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": {
      "id": "<id>"
    },
    "name": "doer_update_todo_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the todo list to update
bodyNoUpdated markdown body content
titleNoUpdated title for the todo list
pinnedNoPin or unpin the todo list
project_idNoReassign to a project ID or null for standalone
pinned_positionNoReorder pinned position
render_markdownNoWhether to return rendered HTML in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It says nothing about partial-update semantics (whether omitted fields are left untouched or cleared), what happens when the id does not exist, required permissions, or that project_id=null detaches the list — all material for a mutation tool.

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?

A single front-loaded sentence with the verb and resource first and the mutable fields following. There is no filler and nothing to trim, even if some of the field enumeration duplicates the schema.

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

Completeness2/5

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

For a seven-parameter mutation tool with no annotations and no output schema, the description is thin: it omits partial-update semantics, error behavior on a bad id, and the effect of render_markdown on the response. The agent knows what the tool is for but not how it behaves.

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%, so every parameter including pinned_position and render_markdown is already documented in the schema. The description enumerates four of the seven fields, which is largely a restatement of schema content and adds no new meaning such as the null-detach behavior of project_id.

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?

The description gives a specific verb ('Update') and resource ('an existing todo list') plus the set of mutable fields (title, body, project assignment, pin state), which distinguishes it from doer_create_todo_list and doer_append_to_todo_list. It stops short of naming any sibling explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no alternatives are mentioned, despite real overlap in the sibling list: doer_append_to_todo_list also changes body content, doer_toggle_pin also changes pin state, and doer_reorder_pinned covers pinned_position. The agent is left to guess which tool to call for a pin change or a body edit.

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