Todoist AI MCP Server

Official

by Doist

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

add-reminders

Add reminders to Todoist tasks using relative time offsets, absolute dates/times, or location-based geofence triggers.

Instructions

Add reminders to tasks. Supports three types: "relative" (minutes before due), "absolute" (specific date/time), or "location" (geofence-triggered). Each reminder must specify a taskId.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`reminders`	Yes	Array of reminders to create (max 25). Each reminder must specify a type: "relative" (minutes before due), "absolute" (specific date/time), or "location" (geofence trigger).

Output Schema

TableJSON Schema

Name	Required	Description
`reminders`	Yes	The created reminders.
`totalCount`	Yes	Total number of reminders created.
`addedReminderIds`	Yes	IDs of the created reminders.

Schema Changelog

Changes observed during successful MCP inspections.

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"

Changed15 schema fields changedv12.5.3Aug 7, 2026
- changedOutput schema / properties / reminders / items / properties / due / description
```
Previous value: -"Due date info (absolute and sometimes relative reminders)."New value: +"Absolute, and sometimes relative, reminders."
```
- changedOutput schema / properties / reminders / items / properties / due / properties / date / description
```
Previous value: -"Due date in ISO format."New value: +"ISO 8601."
```
- changedOutput schema / properties / reminders / items / properties / due / properties / datetime / description
```
Previous value: -"Due datetime in ISO format."New value: +"ISO 8601."
```
- removedOutput schema / properties / reminders / items / properties / due / properties / isRecurring / description
```
Removed value: -"Whether this is a recurring reminder."
```
- removedOutput schema / properties / reminders / items / properties / due / properties / timezone / description
```
Removed value: -"Timezone of the reminder."
```
- removedOutput schema / properties / reminders / items / properties / id / description
```
Removed value: -"The unique ID of the reminder."
```
- changedOutput schema / properties / reminders / items / properties / isUrgent / description
```
Previous value: -"Whether this is an urgent reminder (relative and absolute reminders only)."New value: +"Relative and absolute reminders only."
```
- changedOutput schema / properties / reminders / items / properties / locLat / description
```
Previous value: -"Latitude (location reminders only)."New value: +"Location reminders only."
```
- changedOutput schema / properties / reminders / items / properties / locLong / description
```
Previous value: -"Longitude (location reminders only)."New value: +"Location reminders only."
```
- changedOutput schema / properties / reminders / items / properties / locTrigger / description
```
Previous value: -"Trigger type: on_enter or on_leave (location reminders only)."New value: +"Location reminders only."
```
- changedOutput schema / properties / reminders / items / properties / minuteOffset / description
```
Previous value: -"Minutes before due time to trigger (relative reminders only)."New value: +"Minutes before due. Relative reminders only."
```
- changedOutput schema / properties / reminders / items / properties / name / description
```
Previous value: -"Location name (location reminders only)."New value: +"Location name. Location reminders only."
```
- changedOutput schema / properties / reminders / items / properties / radius / description
```
Previous value: -"Geofence radius in meters (location reminders only)."New value: +"Geofence radius in metres. Location reminders only."
```
- removedOutput schema / properties / reminders / items / properties / taskId / description
```
Removed value: -"The task ID this reminder belongs to."
```
- removedOutput schema / properties / reminders / items / properties / type / description
```
Removed value: -"The type of reminder: relative, absolute, or location."
```
First observedv10.4.2Jul 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The annotations already communicate that this is not read-only and not destructive. The description adds context about reminder types and the taskId requirement, but it does not disclose additional behavioral details such as duplicate behavior, notification delivery defaults, or error conditions.

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 compact and front-loaded. The core action is in the first sentence, followed by a concise list of reminder types and the key taskId constraint, with no redundant content.

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 complexity of the schema with multiple reminder variants, the description gives enough orientation to understand the domain and the three supported modes. The schema covers structural details like maxItems and per-field descriptions, and an output schema exists, so the absence of return-value details is acceptable.

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?

The schema provides very high description coverage (100%), so the description does not need to compensate heavily. It does summarize the three reminder categories and the taskId requirement, but it adds little beyond what the input schema already describes.

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 clearly states the verb and resource: 'Add reminders to tasks.' It also distinguishes this from sibling tools like update-reminders and find-reminders by specifying creation as the operation and enumerating the three reminder types.

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 usage is implied well: when you want to add reminders to tasks, use this tool. However, there is no explicit when-not-to-use guidance or mention of alternatives, such as using update-reminders to modify existing reminders.

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