Skip to main content
Glama
Sign In
Todoist MCP Server

Todoist MCP Server

by greirson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

todoist_section_delete

Delete a Todoist section with all its tasks. Specify the section by ID or search by name within a project for quick removal.

Instructions

Delete a section and all its tasks from Todoist. Can delete by section ID or section name search.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "todoist_section_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
section_idNoSection ID to delete (takes precedence over section_name if both provided)
section_nameNoSection name to search for (case-insensitive partial match)
project_idNoProject ID to narrow down section search when using section_name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses that deletion removes the section and all its tasks, implying destructiveness. However, without annotations, it should more explicitly state permanence, irreversibility, or required permissions. The description adds some value but could be more thorough.

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?

Two concise sentences that front-load the core action and immediately provide two usage options. Every word serves a purpose with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the deletion action and methods, but lacks information about return values, success confirmation, or potential side effects (e.g., cascade to subtasks). Given the absence of an output schema, a brief note on what to expect after execution would improve completeness.

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?

With 100% schema description coverage, the schema already explains each parameter individually. The description adds value by clarifying the relationship between parameters (section_id takes precedence over section_name) and consolidating the two deletion approaches, which aids understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete a section and all its tasks') and resource (section). It also specifies two distinct methods of deletion (by ID or name), which distinguishes it from sibling tools like todoist_section_archive that archive without deleting tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly indicates usage by mentioning deletion methods, but lacks explicit guidance on when to use delete versus archive or other section operations. It does not mention prerequisites like needing a project_id when searching by name, nor does it contrast with alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools