Skip to main content
Glama
Doist

Todoist AI MCP Server

Official
by Doist
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

find-tasks-by-date

Read-onlyIdempotent

Retrieve Todoist tasks by date range, with optional filters for overdue status, labels, and assignee.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoThe maximum number of tasks to return. Default is 10.
cursorNoThe cursor to get the next page of tasks (cursor is obtained from the previous call to this tool, with the same parameters).
labelsNoThe labels to filter the tasks by
daysCountNoThe number of days to get the tasks for, starting from the start date. Default is 1 which means only tasks for the start date.
startDateNoThe start date to get the tasks for. Format: YYYY-MM-DD, or 'today', which by default also includes overdue tasks.
overdueOptionNoHow 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'.
labelsOperatorNoThe operator to use when filtering by labels. This will dictate whether a task has all labels, or some of them. Default is "or".
responsibleUserNoFilter tasks assigned to this user. User ID, name, or email. The current user also includes unassigned tasks.
responsibleUserFilteringNoFilter when responsibleUser is omitted. 'assigned'=assigned to others; 'unassignedOrMe'=unassigned+mine; 'all'=everyone. Default: 'unassignedOrMe'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYesThe found tasks.
hasMoreYes
nextCursorNo
totalCountYesThe total number of tasks in this page.
appliedFiltersYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv13.1.3
    • changedInput schema / properties / responsibleUser / description
      Previous value: -"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."New value: +"Filter tasks assigned to this user. User ID, name, or email. The current user also includes unassigned tasks."
  2. Changed2 schema fields changedv13.0.0
    • 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"
  3. Changed22 schema fields changedv12.5.3
    • changedInput schema / properties / startDate / description
      Previous value: -"The start date to get the tasks for. Format: YYYY-MM-DD or 'today'."New value: +"The start date to get the tasks for. Format: YYYY-MM-DD, or 'today', which by default also includes overdue tasks."
    • 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."
  4. Changed1 schema field changedv12.5.0
    • changedInput schema / properties / limit / description
      Previous value: -"The maximum number of tasks to return."New value: +"The maximum number of tasks to return. Default is 10."
  5. Changed1 schema field changedv10.5.0
    • addedOutput schema / properties / tasks / items / properties / addedAt
      Added value: +{
+  "description": "When the task was created (ISO 8601 format).",
+  "type": "string"
+}
  6. First observedv10.4.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive traits. The description adds valuable non-obvious behavior: startDate='today' includes overdue items, and the default responsibleUserFiltering='unassignedOrMe' excludes tasks assigned to others. This gives an agent meaningful insight beyond the schema 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.

Conciseness5/5

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

Two sentences with no filler. The core action is front-loaded, followed only by the two non-obvious defaults that an agent would most likely misjudge. 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 rich input schema, output schema, and safety annotations, the description is largely sufficient. It highlights the most important defaults and the date-range scope. It could slightly improve by mentioning when to use this instead of sibling find tools, but the schema covers the remaining parameter semantics.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds interpretive value by calling out that 'today' includes overdue items and that the default responsible filtering excludes other people's tasks, which helps an agent understand real-world consequences of the parameters.

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 opens with a specific verb and resource: 'Get tasks by date range.' This clearly distinguishes it from sibling tools like find-tasks or find-completed-tasks because the date-range scope is explicit. It also communicates two important default behaviors that refine the tool's purpose.

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 the tool is for date-based task retrieval by saying 'Get tasks by date range,' but it does not explicitly state when to prefer this tool over find-tasks or find-completed-tasks. It provides useful behavioral context about defaults but no explicit exclusions or alternative routing.

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

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