Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_delete_project

Remove a Todoist project permanently by specifying its ID to clean up your workspace and manage project organization.

Instructions

Delete a project by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe ID of the project to delete

Implementation Reference

  • The handler logic for the 'todoist_delete_project' tool. Validates input using isProjectIdArgs type guard, calls todoistClient.deleteProject(projectId), and returns a success message.
    if (name === "todoist_delete_project") {
      if (!isProjectIdArgs(args)) {
        throw new Error("Invalid arguments for todoist_delete_project");
      }
    
      await todoistClient.deleteProject(args.projectId);
      
      return {
        content: [{ 
          type: "text", 
          text: `Project ${args.projectId} deleted successfully` 
        }],
        isError: false,
      };
    }
  • The Tool object definition specifying the name, description, and input schema (requiring projectId) for the todoist_delete_project tool.
    const DELETE_PROJECT_TOOL: Tool = {
      name: "todoist_delete_project",
      description: "Delete a project by its ID",
      inputSchema: {
        type: "object",
        properties: {
          projectId: {
            type: "string",
            description: "The ID of the project to delete"
          }
        },
        required: ["projectId"]
      }
    };
  • src/index.ts:1083-1121 (registration)
    Registration of the todoist_delete_project tool (as DELETE_PROJECT_TOOL) in the list of tools returned by the ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        // Task tools
        CREATE_TASK_TOOL,
        QUICK_ADD_TASK_TOOL,
        GET_TASKS_TOOL,
        GET_TASK_TOOL,
        UPDATE_TASK_TOOL,
        DELETE_TASK_TOOL,
        COMPLETE_TASK_TOOL,
        REOPEN_TASK_TOOL,
        SEARCH_TASKS_TOOL,
        MOVE_TASK_TOOL,
        BULK_MOVE_TASKS_TOOL,
        // Project tools
        GET_PROJECTS_TOOL,
        GET_PROJECT_TOOL,
        CREATE_PROJECT_TOOL,
        UPDATE_PROJECT_TOOL,
        DELETE_PROJECT_TOOL,
        // Section tools
        GET_SECTIONS_TOOL,
        CREATE_SECTION_TOOL,
        UPDATE_SECTION_TOOL,
        DELETE_SECTION_TOOL,
        // Label tools
        CREATE_LABEL_TOOL,
        GET_LABEL_TOOL,
        GET_LABELS_TOOL,
        UPDATE_LABEL_TOOL,
        DELETE_LABEL_TOOL,
        // Comment tools
        CREATE_COMMENT_TOOL,
        GET_COMMENT_TOOL,
        GET_COMMENTS_TOOL,
        UPDATE_COMMENT_TOOL,
        DELETE_COMMENT_TOOL,
      ],
    }));
  • Type guard helper function isProjectIdArgs used to validate the input arguments for project-related tools, including todoist_delete_project.
    function isProjectIdArgs(args: unknown): args is {
      projectId: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "projectId" in args &&
        typeof (args as { projectId: string }).projectId === "string"
      );
    }
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. While 'Delete' implies a destructive mutation, it doesn't specify whether this action is reversible, what permissions are required, whether it affects child resources (tasks/sections), or what happens on success/failure. 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.

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and understandable.

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 deletion tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens to associated tasks/comments, whether deletion is permanent, what the response looks like, or error conditions. Given the complexity and risk of deletion, more context is needed.

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 'projectId'. Since schema description coverage is 100% (the schema already documents 'The ID of the project to delete'), the description adds minimal value beyond what's in the structured schema. This meets the baseline for high schema coverage.

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 'Delete a project by its ID' clearly states the verb (delete) and resource (project), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like todoist_delete_task or todoist_delete_section, but the resource specificity (project) provides implicit distinction.

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., project must exist), consequences (e.g., tasks within the project might be affected), or when to choose deletion over other operations like todoist_update_project.

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/vitalio-sh/todoist-mcp-server-ext'

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