Skip to main content
Glama
mikemc

Todoist MCP Server

by mikemc

todoist_delete_task

Remove a task from Todoist by specifying its task ID, enabling efficient task management and cleanup within the Todoist MCP Server environment.

Instructions

Delete a task from Todoist

Args: task_id: ID of the task to delete

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes

Implementation Reference

  • The handler function that implements the logic to delete a Todoist task by ID. It verifies the task exists, deletes it using the Todoist API client, and returns a success message with the task content.
    def todoist_delete_task(ctx: Context, task_id: str) -> str:
        """Delete a task from Todoist
    
        Args:
            task_id: ID of the task to delete
        """
        todoist_client = ctx.request_context.lifespan_context.todoist_client
    
        try:
            logger.info(f"Deleting task with ID: {task_id}")
    
            try:
                task = todoist_client.get_task(task_id=task_id)
                task_content = task.content
            except Exception as error:
                logger.warning(f"Error getting task with ID: {task_id}: {error}")
                return f"Could not verify task with ID: {task_id}. Deletion aborted."
    
            is_success = todoist_client.delete_task(task_id=task_id)
    
            logger.info(f"Task deleted successfully: {task_id}")
            return f"Successfully deleted task: {task_content} (ID: {task_id})"
        except Exception as error:
            logger.error(f"Error deleting task: {error}")
            return f"Error deleting task: {str(error)}"
  • src/main.py:92-92 (registration)
    The registration of the todoist_delete_task tool using the MCP decorator mcp.tool().
    mcp.tool()(todoist_delete_task)
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 tool deletes a task, implying a destructive mutation, but doesn't specify whether deletion is permanent, reversible, requires specific permissions, or has side effects (e.g., affecting subtasks). This leaves significant gaps in understanding the tool's behavior 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.

Conciseness3/5

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

The description is brief and front-loaded with the core action, but the 'Args:' section is redundant since the schema already documents parameters. This adds unnecessary length without new value, though the overall text remains relatively concise at two sentences.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover critical aspects like return values (e.g., success confirmation, error handling), behavioral nuances (e.g., deletion permanence), or integration with sibling tools, leaving the agent under-informed for safe and effective use.

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 adds meaningful context for the single parameter 'task_id' by explaining it's 'ID of the task to delete', which clarifies its purpose beyond the schema's minimal title 'Task Id'. With 0% schema description coverage and only one parameter, this compensation is adequate, though it could benefit from format examples (e.g., numeric vs. string ID).

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 ('Delete') and resource ('a task from Todoist'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'todoist_close_task' or 'todoist_delete_project', which would require more specific language about what distinguishes task deletion from other deletion or completion operations.

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 like 'todoist_close_task' or 'todoist_delete_project'. It lacks context about prerequisites (e.g., task must exist), consequences (e.g., permanent deletion vs. archiving), or typical use cases, leaving the agent with minimal usage direction.

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