Skip to main content
Glama
mikemc

Todoist MCP Server

by mikemc

todoist_delete_project

Removes a specific project from your Todoist account using the project ID. Streamlines project management by enabling quick deletion of unnecessary or completed projects.

Instructions

Deletes a project from the user's Todoist account

Args: project_id: ID of the project to delete

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes

Implementation Reference

  • The handler function that implements the logic to delete a Todoist project by its ID. It retrieves the project for confirmation, calls the Todoist API to delete it, and returns a success message with the project name or an error.
    def todoist_delete_project(ctx: Context, project_id: str) -> str:
        """Deletes a project from the user's Todoist account
    
        Args:
            project_id: ID of the project to delete
        """
        todoist_client = ctx.request_context.lifespan_context.todoist_client
    
        try:
            logger.info(f"Deleting project with ID: {project_id}")
    
            # Capture project name for meaningful success/failure messages
            try:
                project = todoist_client.get_project(project_id=project_id)
                project_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}. Deletion aborted."
    
            is_success = todoist_client.delete_project(project_id=project_id)
    
            logger.info(f"Project deleted successfully: {project_id} ({project_name})")
            return f"Successfully deleted project: {project_name} (ID: {project_id})"
    
        except Exception as error:
            logger.error(f"Error deleting project: {error}")
            return f"Error deleting project: {str(error)}"
  • src/main.py:76-76 (registration)
    Registers the todoist_delete_project function as an MCP tool using the FastMCP decorator.
    mcp.tool()(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 destructive action ('Deletes') but lacks critical details: whether deletion is permanent or reversible, if it cascades to tasks/sections, required permissions, error conditions, or confirmation prompts. This is inadequate for a destructive operation.

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 brief and front-loaded with the core purpose in the first sentence. The 'Args:' section adds parameter details without redundancy. While efficient, it could be more structured (e.g., bullet points) but avoids unnecessary verbosity.

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?

For a destructive tool with no annotations and no output schema, the description is incomplete. It misses behavioral implications (irreversibility, cascading effects), error handling, and response format. Given the complexity of deletion operations and lack of structured data, more context is needed for safe usage.

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?

Schema description coverage is 0%, so the schema provides no parameter documentation. The description adds the parameter 'project_id' with a brief explanation ('ID of the project to delete'), which clarifies its purpose. However, it doesn't specify format constraints (e.g., numeric vs. string), validation rules, or where to obtain the ID, leaving 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 action ('Deletes') and resource ('a project from the user's Todoist account'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like todoist_delete_task or todoist_delete_section, which perform similar deletion operations on different resource types.

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), exclusions, or comparisons to sibling tools like todoist_update_project for modifying instead of deleting.

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