Skip to main content
Glama
elizagarate

Things MCP Server

by elizagarate

update_todo

Update an existing todo's properties: title, notes, schedule, deadline, tags, completion status, or move it to another project or heading.

Instructions

Update an existing todo in Things

Args: id: ID of the todo to update title: New title notes: New notes when: New schedule (today, tomorrow, evening, anytime, someday, or YYYY-MM-DD). Use YYYY-MM-DD@HH:MM format to add a reminder (e.g., 2024-01-15@14:30) deadline: New deadline (YYYY-MM-DD) tags: New tags completed: Mark as completed canceled: Mark as canceled list: The title of a project or area to move the to-do into list_id: The ID of a project or area to move the to-do into (takes precedence over list) heading: The heading title to move the to-do under heading_id: The heading ID to move the to-do under (takes precedence over heading)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
titleNo
notesNo
whenNo
deadlineNo
tagsNo
completedNo
canceledNo
listNo
list_idNo
headingNo
heading_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler function 'update_todo' decorated with @mcp.tool that accepts parameters (id, title, notes, when, deadline, tags, completed, canceled, list, list_id, heading, heading_id), calls url_scheme.update_todo() to build the Things URL, executes it, and returns a confirmation string.
    @mcp.tool
    async def update_todo(
        id: str,
        title: str = None,
        notes: str = None,
        when: str = None,
        deadline: str = None,
        tags: List[str] = None,
        completed: bool = None,
        canceled: bool = None,
        list: str = None,
        list_id: str = None,
        heading: str = None,
        heading_id: str = None
    ) -> str:
        """Update an existing todo in Things
    
        Args:
            id: ID of the todo to update
            title: New title
            notes: New notes
            when: New schedule (today, tomorrow, evening, anytime, someday, or YYYY-MM-DD).
                Use YYYY-MM-DD@HH:MM format to add a reminder (e.g., 2024-01-15@14:30)
            deadline: New deadline (YYYY-MM-DD)
            tags: New tags
            completed: Mark as completed
            canceled: Mark as canceled
            list: The title of a project or area to move the to-do into
            list_id: The ID of a project or area to move the to-do into (takes precedence over list)
            heading: The heading title to move the to-do under
            heading_id: The heading ID to move the to-do under (takes precedence over heading)
        """
        url = url_scheme.update_todo(
            id=id,
            title=title,
            notes=notes,
            when=when,
            deadline=deadline,
            tags=tags,
            completed=completed,
            canceled=canceled,
            list=list,
            list_id=list_id,
            heading=heading,
            heading_id=heading_id
        )
        url_scheme.execute_url(url)
        return f"Updated todo with ID: {id}"
  • The URL construction helper function 'update_todo' that builds a Things URL for updating an existing todo. Accepts all update parameters, constructs params dict, and calls construct_url('update', ...) with non-None values.
    def update_todo(id: str, title: Optional[str] = None, notes: Optional[str] = None,
                    when: Optional[str] = None, deadline: Optional[str] = None,
                    tags: Optional[list[str]] = None, completed: Optional[bool] = None,
                    canceled: Optional[bool] = None, list: Optional[str] = None,
                    list_id: Optional[str] = None, heading: Optional[str] = None,
                    heading_id: Optional[str] = None) -> str:
        """Construct URL to update an existing todo.
    
        Args:
            id: UUID of the todo to update
            title: New title
            notes: New notes
            when: Reschedule the todo. Accepts:
                - Keywords: "today", "tomorrow", "evening", "anytime", "someday"
                - Date: "yyyy-mm-dd" or natural language ("in 3 days", "next tuesday")
                - DateTime (adds reminder): "yyyy-mm-dd@HH:MM" (e.g., "2024-01-15@14:30")
            deadline: New deadline (yyyy-mm-dd)
            tags: New tags (replaces existing)
            completed: Mark as completed
            canceled: Mark as canceled
            list: Title of project/area to move to
            list_id: UUID of project/area to move to (takes precedence over list)
            heading: Heading title to move under
            heading_id: UUID of heading to move under (takes precedence over heading)
        """
        params = {
            'id': id,
            'title': title,
            'notes': notes,
            'when': when,
            'deadline': deadline,
            'tags': tags,
            'completed': completed,
            'canceled': canceled,
            'list': list,
            'list-id': list_id,
            'heading': heading,
            'heading-id': heading_id
        }
        return construct_url('update', {k: v for k, v in params.items() if v is not None})
  • The FastMCP server instance 'mcp = FastMCP("Things")' which handles the @mcp.tool decorator that registers the update_todo function as an MCP tool.
    mcp = FastMCP("Things")
  • Tests for the update_todo URL construction helper, covering minimal parameters and all parameters including tags, boolean flags, list/heading IDs.
    class TestUpdateTodo:
        """Test the update_todo function."""
        
        @patch('things.token')
        def test_update_todo_minimal(self, mock_token):
            """Test updating todo with minimal parameters."""
            mock_token.return_value = "auth-token"
            url = update_todo("todo-123")
            assert "id=todo-123" in url
            assert "auth-token=auth-token" in url
        
        @patch('things.token')
        def test_update_todo_full(self, mock_token):
            """Test updating todo with all parameters."""
            mock_token.return_value = "auth-token"
            url = update_todo(
                id="todo-123",
                title="Updated Title",
                notes="Updated notes",
                when="tomorrow",
                deadline="2024-02-01",
                tags=["updated", "tag"],
                completed=True,
                canceled=False,
                list="Inbox",
                list_id="inbox-id",
                heading="New Heading",
                heading_id="heading-uuid"
            )
            
            assert "id=todo-123" in url
            assert "title=Updated%20Title" in url
            assert "notes=Updated%20notes" in url
            assert "when=tomorrow" in url
            assert "deadline=2024-02-01" in url
            assert "tags=updated%2Ctag" in url
            assert "completed=true" in url
            assert "canceled=false" in url
            assert "list=Inbox" in url
            assert "list-id=inbox-id" in url
            assert "heading=New%20Heading" in url
            assert "heading-id=heading-uuid" in url
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'Update' which implies mutation, but does not disclose side effects, required permissions, error handling, or return values. This is insufficient 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.

Conciseness4/5

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

The description is organized with an 'Args:' section listing parameters, which is readable. While lengthy due to 12 parameters, every sentence adds value. It could be slightly more concise but is not verbose.

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

Completeness3/5

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

Given the tool's complexity (12 parameters, no schema descriptions, and an output schema exists), the description covers parameter semantics well but lacks behavioral context such as what happens if the id does not exist or whether partial updates are supported. The output schema presumably handles return values, so that gap is mitigated.

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 description coverage, the description compensates fully by explaining each parameter, including format details for 'when' and precedence for 'list_id' vs 'list'. This adds significant meaning beyond the bare input schema.

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 'Update an existing todo in Things', which is a specific verb+resource combination. It distinguishes from sibling tools like add_todo and update_project by focusing on updating existing todos.

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 for updating existing todos but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The context is implied by the tool's purpose.

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

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