Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_delete_section

Remove sections from Todoist projects by specifying the section ID to organize tasks and maintain project structure.

Instructions

Delete a section by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionIdYesThe ID of the section to delete

Implementation Reference

  • Handler for 'todoist_delete_section' tool: validates input using isSectionIdArgs, calls todoistClient.deleteSection(sectionId), and returns success message.
    if (name === "todoist_delete_section") {
      if (!isSectionIdArgs(args)) {
        throw new Error("Invalid arguments for todoist_delete_section");
      }
    
      await todoistClient.deleteSection(args.sectionId);
      
      return {
        content: [{ 
          type: "text", 
          text: `Section ${args.sectionId} deleted successfully` 
        }],
        isError: false,
      };
    }
  • Tool schema definition for 'todoist_delete_section', specifying input schema requiring 'sectionId'.
    const DELETE_SECTION_TOOL: Tool = {
      name: "todoist_delete_section",
      description: "Delete a section by its ID",
      inputSchema: {
        type: "object",
        properties: {
          sectionId: {
            type: "string",
            description: "The ID of the section to delete"
          }
        },
        required: ["sectionId"]
      }
    };
  • src/index.ts:1103-1108 (registration)
    Registration of DELETE_SECTION_TOOL in the list of tools returned by ListToolsRequestSchema handler.
    // Section tools
    GET_SECTIONS_TOOL,
    CREATE_SECTION_TOOL,
    UPDATE_SECTION_TOOL,
    DELETE_SECTION_TOOL,
    // Label tools
  • Type guard helper 'isSectionIdArgs' used to validate arguments in the delete section handler.
    function isSectionIdArgs(args: unknown): args is {
      sectionId: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "sectionId" in args &&
        typeof (args as { sectionId: string }).sectionId === "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. It states the destructive action ('Delete') but lacks critical details: whether deletion is permanent or reversible, what happens to tasks within the section, required permissions, or error handling. This is inadequate 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 wasted words, making it highly efficient and front-loaded. Every word earns its place by conveying the core action and target.

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 doesn't address behavioral aspects like permanence, side effects on tasks, or response format, leaving significant gaps in understanding how to use it safely and effectively.

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 100%, with the parameter 'sectionId' fully documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., format examples or constraints), so it meets the baseline for high coverage without compensating value.

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 section by its ID'), making the purpose immediately understandable. However, it doesn't differentiate this from other deletion tools like todoist_delete_project or todoist_delete_task, which would require mentioning it specifically removes a section rather than other entities.

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 on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing section ID), exclusions, or how it differs from similar tools like todoist_delete_project, leaving the agent to infer usage from context alone.

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