Skip to main content
Glama
greirson

Todoist MCP Server

todoist_task_get

Retrieve Todoist tasks using filters like date, priority, project, or label. Get specific tasks by ID or search by name.

Instructions

Retrieve tasks from Todoist. Use 'filter' for Todoist filter syntax (e.g., 'today', 'p1') or 'task_name' for simple text search in task content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idNoGet a specific task by its ID (optional, takes precedence over filtering)
project_idNoFilter tasks by project ID (optional)
label_idNoFilter tasks by label ID (optional)
priorityNoFilter tasks by priority level 1 (highest) to 4 (lowest) (optional)
limitNoMaximum number of tasks to return (optional)
due_beforeNoReturn only tasks due strictly before this date (YYYY-MM-DD, optional)
due_afterNoReturn only tasks due strictly after this date (YYYY-MM-DD, optional)
filterNoTodoist filter string like 'today', 'overdue', 'p1' (optional)
langNoLanguage for filter parsing, defaults to 'en' (optional)
task_nameNoFilter tasks by name/content using partial text matching (case-insensitive, optional)
Behavior2/5

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

No annotations provided, so description must carry behavioral disclosure. It only states retrieval without mentioning cardinality, pagination, side effects, or read-only nature. Key behaviors like parameter precedence (task_id overrides filters) are omitted.

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. No unnecessary words; every part contributes to understanding. Second sentence provides actionable guidance.

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?

Despite the tool having 10 parameters and no output schema or annotations, the description only covers two parameters minimally. It omits many filtering options (project_id, label_id, priority, due dates, limit) and does not explain output behavior, making it incomplete for effective use.

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 has 100% description coverage, so baseline is 3. Description adds marginal value by summarizing filter and task_name usage, but does not significantly enhance understanding beyond schema. The examples ('today', 'p1') are already in schema description.

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?

Description clearly states it retrieves tasks from Todoist, specifying two main filtering methods (filter and task_name). This verb-resource pair is unambiguous and distinguishes it from sibling tools that create, update, or delete 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?

Provides guidance on using 'filter' vs 'task_name' for searching, but does not explain when to use task_id for single task retrieval or how this tool compares to other task-related tools. The instruction is helpful but incomplete for choosing the right parameter.

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