Todoist AI MCP Server

Official

by Doist

Overview Schema Related Servers Score Discussions

TypeScript

Remote

find-tasks-by-date

Read-onlyIdempotent

Get tasks for a date range, including overdue tasks. Filter by labels and assigned user to narrow results.

Instructions

Get tasks by date range. startDate='today' includes overdue items. Default responsibleUserFiltering='unassignedOrMe' excludes others' tasks. Person-specific queries (summaries, plans, reports) require responsibleUser.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	The maximum number of tasks to return.
`cursor`	No	The cursor to get the next page of tasks (cursor is obtained from the previous call to this tool, with the same parameters).
`labels`	No	The labels to filter the tasks by
`daysCount`	No	The number of days to get the tasks for, starting from the start date. Default is 1 which means only tasks for the start date.
`startDate`	No	The start date to get the tasks for. Format: YYYY-MM-DD or 'today'.
`overdueOption`	No	How to handle overdue tasks. 'overdue-only' to get only overdue tasks, 'include-overdue' to include overdue tasks along with tasks for the specified date(s), and 'exclude-overdue' to exclude overdue tasks. Default is 'include-overdue'.
`labelsOperator`	No	The operator to use when filtering by labels. This will dictate whether a task has all labels, or some of them. Default is "or".
`responsibleUser`	No	Filter tasks assigned to this user. User ID, name, or email. For personal queries (summaries, plans, reports), set to current user from user-info to exclude collaborators.
`responsibleUserFiltering`	No	Filter when responsibleUser is omitted. 'assigned'=assigned to others; 'unassignedOrMe'=unassigned+mine; 'all'=everyone. Default: 'unassignedOrMe'.

Output Schema

TableJSON Schema

Name	Required	Description
`tasks`	Yes	The found tasks.
`hasMore`	Yes	Whether there are more results available.
`nextCursor`	No	Cursor for the next page of results.
`totalCount`	Yes	The total number of tasks in this page.
`appliedFilters`	Yes	The filters that were applied to the search.

Tool Definition Quality

A3.9/5.0

Behavior4/5

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

Discloses that startDate='today' includes overdue items and default responsibleUserFiltering excludes others' tasks, adding value beyond annotations (readOnlyHint, etc.). No contradiction.

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, no wasted words. First sentence states purpose, second adds critical defaults and usage hint. Highly efficient.

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?

With full schema coverage, annotations, and output schema present, description adequately covers key behaviors. Could mention pagination but not essential.

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?

Input schema has full description coverage (100%), baseline is 3. Description adds meaningful context about default behaviors and special values (e.g., startDate='today'), enhancing understanding.

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?

Clearly states 'Get tasks by date range' and adds context about defaults. However, it does not explicitly differentiate from sibling tools like find-tasks which may also support date filtering.

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 when to set responsibleUser for person-specific queries, but does not mention when to use this tool over alternatives or provide exclusions.

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

Install Server

Latest Blog Posts

Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

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/Doist/todoist-ai'

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