Todoist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

find-tasks

Read-onlyIdempotent

Search Todoist tasks by text, project, section, parent, user, labels, or filter strings; at least one filter is required.

Instructions

Find tasks by text search, project/section/parent container, responsible user, labels, a raw Todoist filter string, or a saved filter by ID or name (filterIdOrName). At least one filter must be provided.

Input 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).
`filter`	No	A raw Todoist filter query string (e.g. "today", "p1", "##Work", "(today \| overdue) & p1"). Combined with other filters using AND. Cannot be used with projectId, sectionId, parentId, or filterIdOrName.
`labels`	No	The labels to filter the tasks by
`parentId`	No	Find subtasks of this parent task.
`projectId`	No	Find tasks in this project. Project ID should be an ID string, or the text "inbox", for inbox tasks.
`sectionId`	No	Find tasks in this section.
`searchText`	No	The text to search for in tasks.
`filterIdOrName`	No	The ID or name of a saved Todoist filter. The filter's query will be fetched and used to find tasks. Cannot be used with the `filter` parameter, projectId, sectionId, or parentId.
`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	Find tasks assigned to this user. Can be a user ID, name, or email address. The current user also includes unassigned tasks.
`responsibleUserFiltering`	No	How to filter by responsible user when responsibleUser is not provided. "assigned" = only tasks assigned to others; "unassignedOrMe" = only unassigned tasks or tasks assigned to me; "all" = all tasks regardless of assignment. Default value will be `unassignedOrMe`.

Output 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.

Changed2 schema fields changedv13.8.4Nov 2, 2026
- removedOutput schema / properties / tasks / items / properties / recurring / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "string"
-  }
-]
```
- addedOutput schema / properties / tasks / items / properties / recurring / type
```
Added value: +[
+  "boolean",
+  "string"
+]
```
Changed1 schema field changedv13.3.0Sep 18, 2026
- changedOutput schema / properties / tasks / items / properties / duration / description
```
Previous value: -"e.g. \"2h30m\"."New value: +"e.g. \"2h30m\", or \"3d\" for a day-based duration."
```
Changed1 schema field changedv13.2.7Sep 16, 2026
- addedOutput schema / properties / tasks / items / properties / isDeleted
```
Added value: +{
+  "description": "True when deleted; absent otherwise.",
+  "type": "boolean"
+}
```

Changed1 schema field changedv13.1.3Sep 2, 2026

changedInput schema / properties / responsibleUser / description

Previous value: -"Find tasks assigned to this user. Can be a user ID, name, or email address."New value: +"Find tasks assigned to this user. Can be a user ID, name, or email address. The current user also includes unassigned tasks."

Changed2 schema fields changedv13.0.0Aug 20, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed21 schema fields changedv12.5.3Aug 7, 2026
- removedOutput schema / properties / appliedFilters / description
```
Removed value: -"The filters that were applied to the search."
```
- removedOutput schema / properties / hasMore / description
```
Removed value: -"Whether there are more results available."
```
- removedOutput schema / properties / nextCursor / description
```
Removed value: -"Cursor for the next page of results."
```
- changedOutput schema / properties / tasks / items / properties / addedAt / description
```
Previous value: -"When the task was created (ISO 8601 format)."New value: +"ISO 8601."
```
- removedOutput schema / properties / tasks / items / properties / assignedByUid / description
```
Removed value: -"The UID of the user who assigned this task."
```
- changedOutput schema / properties / tasks / items / properties / checked / description
```
Previous value: -"Whether the task is checked/completed."New value: +"Whether the task is completed."
```
- changedOutput schema / properties / tasks / items / properties / completedAt / description
```
Previous value: -"When the task was completed (ISO 8601 format)."New value: +"ISO 8601."
```
- changedOutput schema / properties / tasks / items / properties / content / description
```
Previous value: -"The task title/content."New value: +"Task title."
```
- changedOutput schema / properties / tasks / items / properties / deadlineDate / description
```
Previous value: -"The deadline date of the task (ISO 8601 format)."New value: +"ISO 8601."
```
- removedOutput schema / properties / tasks / items / properties / description / description
```
Removed value: -"The task description."
```
- changedOutput schema / properties / tasks / items / properties / dueDate / description
```
Previous value: -"The due date of the task (ISO 8601 format)."New value: +"ISO 8601."
```
- changedOutput schema / properties / tasks / items / properties / duration / description
```
Previous value: -"The duration of the task (e.g., \"2h30m\")."New value: +"e.g. \"2h30m\"."
```
- removedOutput schema / properties / tasks / items / properties / id / description
```
Removed value: -"The unique ID of the task."
```
- changedOutput schema / properties / tasks / items / properties / isUncompletable / description
```
Previous value: -"Whether the task is uncompletable (organizational header)."New value: +"An organizational header, not a real task."
```
- removedOutput schema / properties / tasks / items / properties / labels / description
```
Removed value: -"The labels attached to this task."
```
- removedOutput schema / properties / tasks / items / properties / parentId / description
```
Removed value: -"The ID of the parent task (for subtasks)."
```
- changedOutput schema / properties / tasks / items / properties / priority / description
```
Previous value: -"The priority level: p1 (highest), p2 (high), p3 (medium), p4 (lowest)."New value: +"p1 is highest, p4 lowest."
```
- removedOutput schema / properties / tasks / items / properties / projectId / description
```
Removed value: -"The ID of the project this task belongs to."
```
- changedOutput schema / properties / tasks / items / properties / recurring / description
```
Previous value: -"Whether the task is recurring, or the recurrence string."New value: +"False when not recurring, otherwise the recurrence string."
```
- removedOutput schema / properties / tasks / items / properties / responsibleUid / description
```
Removed value: -"The UID of the user responsible for this task."
```
- removedOutput schema / properties / tasks / items / properties / sectionId / description
```
Removed value: -"The ID of the section this task belongs to."
```
Changed1 schema field changedv10.5.0Jul 10, 2026
- addedOutput schema / properties / tasks / items / properties / addedAt
```
Added value: +{
+  "description": "When the task was created (ISO 8601 format).",
+  "type": "string"
+}
```
First observedv10.4.2Jul 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds the non-obvious behavioral constraint that at least one filter must be supplied, but it does not add further context about pagination, filter-combination behavior, or permission requirements beyond what the schema provides.

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 a single front-loaded sentence plus a brief mandatory-filter constraint. It communicates the core capability and the key validation rule without repetition or filler.

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 rich annotations, 100% schema coverage, and an output schema, the description covers the essential purpose and the at-least-one-filter rule. It is nearly complete, though it could better route the agent among its date-oriented and completed-task siblings.

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 input schema already documents all 12 parameters in detail. The description lists the filtering modes but adds no substantive parameter semantics beyond what is already present in the schema; baseline 3 is appropriate.

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 ('Find') and resource ('tasks') and enumerates the supported filtering modes: text search, project/section/parent, responsible user, labels, raw Todoist filter, and saved filter. It does not explicitly distinguish this tool from close siblings like find-tasks-by-date or find-completed-tasks, so it falls short of a 5.

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 includes the important constraint that at least one filter must be provided, which is useful usage guidance. However, it does not say when to use this tool versus find-tasks-by-date, find-completed-tasks, or search, so the alternative-selection guidance is implied rather than explicit.

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