Skip to main content
Glama
greirson

Todoist MCP Server

todoist_tasks_bulk_complete

Bulk complete tasks in Todoist by filtering by project, priority, due date, or content text.

Instructions

Complete multiple tasks at once based on search criteria. Efficiently mark many tasks as done.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoComplete tasks from this project ID (optional)
priorityNoComplete tasks with this priority level 1 (highest) to 4 (lowest) (optional)
due_beforeNoComplete tasks due before this date (YYYY-MM-DD) (optional)
due_afterNoComplete tasks due after this date (YYYY-MM-DD) (optional)
content_containsNoComplete 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 provided, so the description must bear the full burden. It states the tool 'completes' tasks, which implies an irreversible action, but does not clarify if it can be undone, authorization needs, or side effects. The transparency is adequate but not detailed.

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 two sentences, no filler, and front-loaded with the key verb and purpose. Every word earns its place.

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 the tool has 5 optional parameters and no output schema, the description provides sufficient context for what the tool does. It could be slightly more explicit about the nature of the criteria, but the schema covers specifics. The description is complete enough for an agent to understand when to invoke it.

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 the schema already describes all parameters. The description adds no additional meaning beyond 'search criteria'. Baseline of 3 is appropriate as it neither harms nor significantly enhances understanding.

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 tool's purpose: completing multiple tasks at once based on search criteria. It uses specific verbs ('Complete', 'mark as done') and the resource ('multiple tasks'), effectively distinguishing it from single-task completion tools.

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 implies use for bulk completion but does not explicitly state when to use this tool versus alternatives like todoist_task_complete for single tasks or other bulk operations. No exclusions or alternatives are mentioned.

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