Skip to main content
Glama
mikemc

Todoist MCP Server

by mikemc

todoist_add_project

Add a new project to Todoist with customizable options such as name, color, parent project ID, favorite status, and view style for better task organization and management.

Instructions

Create a new project in Todoist

Args: name: Name of the project color: Color of the project (optional) parent_id: ID of the parent project for creating sub-projects (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
nameYes
parent_idNo
view_styleNo

Implementation Reference

  • The main handler function that implements the logic for adding a new Todoist project using the Todoist API, including parameter validation and error handling.
    def todoist_add_project(
        ctx: Context,
        name: str,
        color: Optional[str] = None,
        parent_id: Optional[str] = None,
        is_favorite: Optional[bool] = None,
        view_style: Optional[str] = None
    ) -> str:
        """Create a new project in Todoist
    
        Args:
            name: Name of the project
            color: Color of the project (optional)
            parent_id: ID of the parent project for creating sub-projects (optional)
            is_favorite: Whether the project should be marked as favorite (optional)
            view_style: View style of the project, either 'list' or 'board' (optional)
        """
        todoist_client = ctx.request_context.lifespan_context.todoist_client
    
        try:
            logger.info(f"Creating project: {name}")
    
            project_params = {
                "name": name
            }
    
            # Add optional parameters efficiently
            if color:
                project_params["color"] = color
            if parent_id:
                project_params["parent_id"] = parent_id
            if is_favorite is not None:
                project_params["is_favorite"] = is_favorite
            # Validate view_style against API-supported values to prevent errors
            if view_style and view_style in ["list", "board", "calendar"]:
                project_params["view_style"] = view_style
    
            project = todoist_client.add_project(**project_params)
    
            logger.info(f"Project created successfully: {project.id}")
            return json.dumps(project.to_dict(), indent=2, default=str)
        except Exception as error:
            logger.error(f"Error creating project: {error}")
            return f"Error creating project: {str(error)}"
  • src/main.py:74-74 (registration)
    Registers the todoist_add_project function as an MCP tool using the FastMCP tool decorator.
    mcp.tool()(todoist_add_project)
  • src/main.py:12-18 (registration)
    Imports the todoist_add_project handler from the projects module for use in the MCP server.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Create') which implies a write operation, but doesn't mention authentication requirements, rate limits, error conditions, what happens on success (e.g., returns project ID), or whether the operation is idempotent. The description adds minimal behavioral context beyond the basic action.

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 a clear purpose statement followed by a parameter section. Every sentence serves a purpose, though the parameter explanations could be slightly more concise. The information is front-loaded with the main action first.

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?

For a creation tool with 5 parameters and no annotations or output schema, the description provides adequate parameter semantics but lacks important behavioral context. It covers what the tool does and what parameters mean, but doesn't address authentication, error handling, return values, or relationships with sibling tools, leaving gaps for an AI agent.

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?

The description provides clear semantic explanations for all 5 parameters in the 'Args' section, adding significant value beyond the schema which has 0% description coverage. Each parameter is explained with its purpose and optional status, though it doesn't provide format details (like color codes) or constraints beyond what's implied.

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 action ('Create a new project') and resource ('in Todoist'), making the purpose immediately understandable. It distinguishes this tool from siblings like todoist_update_project (modification) and todoist_delete_project (deletion), though it doesn't explicitly contrast with todoist_get_projects (read-only).

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 about when to use this tool versus alternatives. While the purpose implies it's for initial project creation, there's no mention of prerequisites, when to choose todoist_update_project instead, or how it relates to sibling tools like todoist_add_section or todoist_create_task.

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