Skip to main content
Glama
elizagarate

Things MCP Server

by elizagarate

update_project

Update any property of an existing project in Things, from title and notes to schedule, deadline, tags, or completion status.

Instructions

Update an existing project in Things

Args: id: ID of the project 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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
titleNo
notesNo
whenNo
deadlineNo
tagsNo
completedNo
canceledNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler that updates an existing project by delegating to url_scheme.update_project() and executing the URL via url_scheme.execute_url().
    @mcp.tool
    async def update_project(
        id: str,
        title: str = None,
        notes: str = None,
        when: str = None,
        deadline: str = None,
        tags: List[str] = None,
        completed: bool = None,
        canceled: bool = None
    ) -> str:
        """Update an existing project in Things
    
        Args:
            id: ID of the project 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
        """
        url = url_scheme.update_project(
            id=id,
            title=title,
            notes=notes,
            when=when,
            deadline=deadline,
            tags=tags,
            completed=completed,
            canceled=canceled
        )
        url_scheme.execute_url(url)
        return f"Updated project with ID: {id}"
  • URL construction function for update-project command, building parameter dict and delegating to construct_url with the 'update-project' command.
    def update_project(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) -> str:
        """Construct URL to update an existing project.
    
        Args:
            id: UUID of the project to update
            title: New title
            notes: New notes
            when: Reschedule the project. 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
        """
        params = {
            'id': id,
            'title': title,
            'notes': notes,
            'when': when,
            'deadline': deadline,
            'tags': tags,
            'completed': completed,
            'canceled': canceled
        }
        return construct_url('update-project', {k: v for k, v in params.items() if v is not None})
  • Registered as an MCP tool via the @mcp.tool decorator on the FastMCP server instance.
    @mcp.tool
  • Helper function that constructs the Things URL, including auth-token injection for 'update-project' commands and URL encoding of parameters.
    def construct_url(command: str, params: Dict[str, Any]) -> str:
        """Construct a Things URL from command and parameters."""
        # Start with base URL
        url = f"things:///{command}"
    
        # Get authentication token if needed
        if command in ['update', 'update-project']:
            token = things.token()
            if token:
                params['auth-token'] = token
  • Helper that executes a Things URL via subprocess, used by the update_project handler to actually trigger the Things app update.
    def execute_url(url: str) -> None:
        """Execute a Things URL without bringing Things to the foreground.
        
        Security: validates the URL starts with 'things:///' before execution
        to prevent opening arbitrary URLs or executing unintended commands.
        Uses subprocess with argument list (no shell interpolation) to avoid
        command injection vectors.
        """
        if not url.startswith("things:///"):
            raise ValueError(f"Invalid Things URL scheme: {url[:50]}")
        subprocess.run(['open', '-g', url], check=True, capture_output=True)
Behavior3/5

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

With no annotations, the description bears full burden. It lists updateable fields and mentions that 'completed' and 'canceled' mark status, but does not disclose side effects (e.g., whether updating one field resets others), error conditions, or permission requirements.

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 well-structured with an args list, but the argument descriptions are minimal and could be more concise. It is not excessively long but could benefit from tighter phrasing.

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 (8 parameters, no annotations, no when-to-use guidance) and the presence of an output schema (assumed to detail return values), the description is adequate but incomplete. It lacks usage context and behavioral traits.

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?

Input schema coverage is 0%, so description must compensate. It explains the 'when' parameter format in detail (including reminder syntax), but for other parameters like 'title', 'notes', 'tags', it merely repeats the schema name without adding type or format constraints.

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 'Update an existing project in Things' which is a specific verb+resource. It distinguishes from sibling 'update_todo' by focusing on projects, but does not explicitly differentiate from 'add_project'.

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 guidance is provided on when to use this tool vs alternatives (e.g., update_todo for todos, or add_project for new projects). The description is purely parameter-oriented.

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