Skip to main content
Glama
greirson

Todoist MCP Server

todoist_tasks_bulk_delete

Delete multiple Todoist tasks at once using search criteria like project, priority, due dates, or content. Permanently removes matching tasks.

Instructions

Delete multiple tasks at once based on search criteria. Use with caution - this will permanently delete matching tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoDelete tasks from this project ID (optional)
priorityNoDelete tasks with this priority level 1 (highest) to 4 (lowest) (optional)
due_beforeNoDelete tasks due before this date (YYYY-MM-DD) (optional)
due_afterNoDelete tasks due after this date (YYYY-MM-DD) (optional)
content_containsNoDelete tasks containing this text in content (optional)
Behavior3/5

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

No annotations are present, so the description must convey behavioral traits. It states permanent deletion and search criteria but lacks details on error handling, confirmation, rate limits, or maximum tasks. The caution adds some value.

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 sentences with clear front-loading of purpose and a caution. No unnecessary words, well-structured.

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

Completeness4/5

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

Given no output schema, the description adequately explains what the tool does. Could mention return value (e.g., count deleted) but is otherwise complete for a bulk delete operation.

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 coverage is 100%, so baseline is 3. The description only says 'based on search criteria' without adding meaning beyond what the schema already provides for each parameter.

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 'Delete multiple tasks at once based on search criteria.' This is a specific verb (delete) with a resource (tasks) and scope (multiple, search criteria), distinguishing it from single-task delete or bulk update.

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?

Includes a caution about permanent deletion but does not provide explicit guidance on when to use this tool versus alternatives like bulk complete or individual delete. No mention of when not to use it or specific prerequisites.

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

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