Skip to main content
Glama

things_update_todo

Modify existing to-dos in Things 3 by updating titles, notes, due dates, tags, checklists, and completion status using JSON input.

Instructions

Update an existing to-do in Things using JSON API for full feature support

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
notesNo
whenNoSchedule the todo: today/tomorrow/evening (relative), anytime/someday (Things categories), YYYY-MM-DD (specific date), or YYYY-MM-DD@HH:MM (specific time)
deadlineNo
tagsNo
checklist_itemsNoBreak down this todo into smaller, manageable steps using a checklist. Perfect for complex tasks that have multiple components but don't warrant a full project. Each checklist item can be individually checked off, providing visual progress feedback. Use when user mentions "steps", "checklist", "break down into parts", or when a task has multiple actionable components (e.g., "Plan event" → ["Book venue", "Arrange catering", "Send invites"]). Alternative to creating separate todos for multi-step tasks.
list_idNoID of the project or area to add the todo to
listNoName of the project, area, or built-in list (inbox, today, anytime, etc.)
headingNoPlace this todo under a specific heading within the project
completedNo
canceledNo
idYesUnique system-generated ID of the todo to update (alphanumeric, 20-24 chars). NOT the todo title! Use things_get_project, things_get_list, or things_search to find the correct ID first. Example: "AbC123dEf456gHi789JkL"
operationNo

Implementation Reference

  • The 'updateTodo' method inside 'ThingsJSONBuilder' which constructs the update payload and executes the JSON API call.
    async updateTodo(params: UpdateTodoJSONParams): Promise<string> {
      const updateData = {
        type: 'to-do',
        operation: 'update',
        id: params.id,
        attributes: this.convertTodoParams(params)
      };
      
      await executeThingsJSON([updateData]);
      return `✅ To-do updated successfully: "${params.title || 'Updated todo'}"`;
    }
  • Definition and registration of the 'things_update_todo' tool in the 'UpdateJSONToolHandler' class.
    {
      name: 'things_update_todo',
      description: 'Update an existing to-do in Things using JSON API for full feature support',
      schema: UpdateTodoJSONSchema as any
    },
  • Routing logic within the tool handler that invokes 'jsonBuilder.updateTodo' when 'things_update_todo' is called.
    if (toolName === 'things_update_todo') {
      const todoParams = params as z.infer<typeof UpdateTodoJSONSchema>;
      return jsonBuilder.updateTodo(todoParams);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention mutation characteristics, idempotency, error conditions (e.g., invalid ID), or reversibility. The phrase 'JSON API for full feature support' hints at capability but provides no actionable behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is appropriately brief, but wastes valuable descriptive space on implementation details ('JSON API') rather than usage guidance or behavioral traits. Front-loading is adequate with the action verb first, though the latter half of the sentence provides minimal value to the agent.

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?

Inadequate for a complex 13-parameter mutation tool with no output schema and no annotations. The description omits crucial context: that partial updates are supported (only 'id' and 'title' are required), how to obtain the 'id' (despite the schema noting this), or what 'full feature support' actually encompasses.

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

Parameters2/5

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

Schema description coverage is 46% (low), and the description does not compensate by explaining any parameters. Critical parameters like 'operation' (no schema description) and 'deadline' (no schema description) remain undocumented. The description should have clarified the 'id' lookup requirement or partial update behavior given the schema gaps.

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 clearly states the verb 'Update' and resource 'existing to-do in Things', distinguishing it from sibling creation tools (things_add_todo) and project updates (things_update_project). However, 'using JSON API for full feature support' adds implementation detail rather than clarifying functional scope.

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?

No explicit guidance on when to use this versus alternatives, nor any prerequisites mentioned. While 'Update an existing to-do' implicitly contrasts with creating new todos, there is no mention of when to prefer this over other modification methods or that the 'id' parameter requires fetching the todo first.

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/hildersantos/things-mcp'

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