Todoist MCP Server

find-tasks-by-date

Read-onlyIdempotent

Retrieve Todoist tasks for a date or range, with options to include or exclude overdue items and filter by labels or assignee.

Instructions

Get tasks by date range. startDate='today' includes overdue items. Default responsibleUserFiltering='unassignedOrMe' excludes others' tasks.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	The maximum number of tasks to return. Default is 10.
`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', which by default also includes overdue tasks.
`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. The current user also includes unassigned tasks.
`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
`nextCursor`	No
`totalCount`	Yes	The total number of tasks in this page.
`appliedFilters`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv13.3.1Sep 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable behavioral specifics beyond annotations: the semantics of 'today' with overdue inclusion and the default user filtering behavior. No contradiction exists between the description and annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences with no filler. The core action is stated first, and the second sentence packs in two behavior-affecting defaults. It could be slightly more specific about scope but is otherwise well-sized.

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 a rich input schema (100% coverage), output schema, and safety annotations, the description does not need to cover return values or every parameter. It provides the most non-obvious defaults that affect results. The remaining gaps, such as pagination or label behavior, are already handled by the schema and tool output.

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 description coverage is 100%, so the schema already documents all parameters and defaults. The description highlights startDate and responsibleUserFiltering, but these details are already present in the schema property descriptions. It does not add new parameter meaning beyond what the schema already provides.

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?

The description states a clear verb and resource: 'Get tasks by date range.' It conveys the tool's scope precisely. However, it does not explicitly differentiate from sibling tools like find-tasks or find-completed-tasks, relying on the title and schema for that distinction.

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

Usage Guidelines4/5

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

The description gives important usage context by noting that startDate='today' includes overdue items and that the default responsibleUserFiltering='unassignedOrMe' excludes others' tasks. This helps an agent decide whether this tool fits the request or whether parameters need to be changed. It does not explicitly state when to prefer sibling tools or provide negative usage guidance.

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