Skip to main content
Glama
enesjakozh
Johnxjp

Todoist Python MCP Server

by Johnxjp
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

delete_task

Remove tasks from Todoist by specifying their unique ID to clean up completed or unnecessary items from your task list.

Instructions

Delete a task by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes

Implementation Reference

  • todoist_server.py:124-134 (handler)
    The handler function for the 'delete_task' tool, decorated with @mcp.tool() to register it with the MCP server. It takes a task_id, strips quotes, calls the Todoist API to delete the task, and returns success or raises an exception.
    @mcp.tool()
def delete_task(task_id: str):
    """Delete a task by its ID"""
    try:
        task_id = task_id.strip('"')
        is_success = todoist_api.delete_task(task_id=task_id)
        if not is_success:
            raise Exception
        return "Task deleted successfully"
    except Exception as e:
        raise Exception(f"Couldn't delete task {str(e)}")

Tool Definition Quality

C2.9/5.0
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 'Delete' which implies a destructive mutation, but doesn't clarify if deletion is permanent, reversible, requires specific permissions, or has side effects (e.g., affecting related data). This is a significant gap for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is a single, direct sentence with zero waste—it states the action and key parameter concisely. It's appropriately sized for a simple tool and front-loaded with essential information, making it efficient for quick understanding.

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?

Given the tool's destructive nature, lack of annotations, no output schema, and incomplete parameter documentation (0% coverage), the description is inadequate. It doesn't address behavioral risks, usage context, or expected outcomes, leaving critical gaps for safe and effective tool invocation by an AI agent.

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?

The description mentions 'by its ID', which aligns with the single parameter 'task_id' in the schema. However, with 0% schema description coverage, the schema provides no details about the ID format or constraints. The description adds minimal value by implying the parameter's role but doesn't compensate for the coverage gap with specifics like ID syntax or examples.

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 target resource ('a task by its ID'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'complete_task' or 'update_task' which also modify tasks, missing an opportunity to clarify its specific destructive nature versus those alternatives.

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 'complete_task' or 'update_task', nor does it mention prerequisites (e.g., task must exist) or consequences. It merely states what it does without context, leaving the agent to infer usage scenarios.

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/Johnxjp/todoist-mcp-python'

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