Skip to main content
Glama
mikemc

Todoist MCP Server

by mikemc

todoist_update_project

Modify an existing Todoist project by updating its name, color, favorite status, or view style. Use this tool to keep your task management system organized and tailored to your preferences.

Instructions

Update an existing project in Todoist

Args: project_id: ID of the project to update name: New name for the project (optional) color: New color for the project (optional) is_favorite: Whether the project should be marked as favorite (optional) view_style: View style of the project, either 'list' or 'board' (optional)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNo
is_favoriteNo
nameNo
project_idYes
view_styleNo

Implementation Reference

  • The handler function that implements the logic to update a Todoist project. It fetches the project, builds update parameters from inputs, and calls the Todoist API to update.
    def todoist_update_project(
        ctx: Context,
        project_id: str,
        name: Optional[str] = None,
        color: Optional[str] = None,
        is_favorite: Optional[bool] = None,
        view_style: Optional[str] = None
    ) -> str:
        """Update an existing project in Todoist
    
        Args:
            project_id: ID of the project to update
            name: New name for the project (optional)
            color: New color for the project (optional)
            is_favorite: Whether the project should be marked as favorite (optional)
            view_style: View style of the project, either 'list', 'board', or 'calendar' (optional)
        """
        todoist_client = ctx.request_context.lifespan_context.todoist_client
    
        try:
            logger.info(f"Updating project with ID: {project_id}")
    
            # Pre-fetch for validation and meaningful error messages
            try:
                project = todoist_client.get_project(project_id=project_id)
                original_name = project.name
            except Exception as error:
                logger.warning(f"Error getting project with ID: {project_id}: {error}")
                return f"Could not verify project with ID: {project_id}. Update aborted."
    
            update_params = {}
            if name:
                update_params["name"] = name
            if color:
                update_params["color"] = color
            if is_favorite is not None:
                update_params["is_favorite"] = is_favorite
            # Same validation as create to maintain consistency
            if view_style and view_style in ["list", "board", "calendar"]:
                update_params["view_style"] = view_style
    
            if len(update_params) == 0:
                return f"No update parameters provided for project: {original_name} (ID: {project_id})"
    
            updated_project = todoist_client.update_project(project_id, **update_params)
    
            logger.info(f"Project updated successfully: {project_id}")
            return json.dumps(updated_project.to_dict(), indent=2, default=str)
    
        except Exception as error:
            logger.error(f"Error updating project: {error}")
            return f"Error updating project: {str(error)}"
  • src/main.py:75-75 (registration)
    Registration of the todoist_update_project tool using the MCP FastMCP tool decorator.
    mcp.tool()(todoist_update_project)
  • Function signature and docstring defining the input schema (parameters and descriptions) for the tool.
    def todoist_update_project(
        ctx: Context,
        project_id: str,
        name: Optional[str] = None,
        color: Optional[str] = None,
        is_favorite: Optional[bool] = None,
        view_style: Optional[str] = None
    ) -> str:
        """Update an existing project in Todoist
    
        Args:
            project_id: ID of the project to update
            name: New name for the project (optional)
            color: New color for the project (optional)
            is_favorite: Whether the project should be marked as favorite (optional)
            view_style: View style of the project, either 'list', 'board', or 'calendar' (optional)
        """
  • src/main.py:12-18 (registration)
    Import statement bringing the todoist_update_project handler into main.py for registration.
    from .projects import (
        todoist_get_projects,
        todoist_get_project,
        todoist_add_project,
        todoist_update_project,
        todoist_delete_project,
    )
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. It states this is an update operation (implies mutation) but doesn't disclose behavioral traits like: what permissions are required, whether changes are reversible, if partial updates are allowed (implied by optional parameters but not stated), rate limits, or what happens on success/failure. The description is minimal beyond stating it's an update.

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 appropriately sized and front-loaded: the first sentence states the purpose clearly. The parameter explanations are organized in a simple list format. There's no wasted text, though it could be more structured (e.g., separating required vs optional). Every sentence earns its place.

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 no annotations, 0% schema coverage, and no output schema, the description is moderately complete. It covers the purpose and parameters well, but lacks behavioral context (permissions, side effects) and output information. For a mutation tool with 5 parameters, this is adequate but has clear gaps - especially around what happens after the update.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It provides clear semantics for all 5 parameters: identifies 'project_id' as required and others as optional, explains what each parameter controls (e.g., 'name: New name for the project', 'view_style: either 'list' or 'board''). This adds significant value beyond the bare schema, though it doesn't specify format constraints (e.g., color codes).

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 tool's purpose: 'Update an existing project in Todoist' - a specific verb ('Update') and resource ('project'). It distinguishes from siblings like 'todoist_add_project' (create) and 'todoist_delete_project' (delete), but doesn't explicitly contrast with 'todoist_get_project' (read). The purpose is clear but sibling differentiation could be more explicit.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing project), when to choose update over delete+create, or how it differs from similar tools like 'todoist_update_task' or 'todoist_update_section'. The agent must infer usage from the name alone.

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

Related 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/mikemc/todoist-mcp-server'

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