Todoist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

add-sections

Create one or more sections in Todoist projects by specifying section names, project IDs, and optional Markdown descriptions.

Instructions

Add one or more new sections to projects.

Input Schema

Name	Required	Description	Default
`sections`	Yes	The array of sections to add.

Output Schema

Name	Required	Description
`failures`	Yes	Sections that could not be created, with the reason for each.
`sections`	Yes	The created sections.
`totalCount`	Yes	The total number of sections created.
`failureCount`	Yes
`successCount`	Yes
`totalRequested`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv13.8.0Oct 29, 2026

removedOutput schema / properties / failureCount / description
```
Removed value: -"The number of failed section creations."
```

changedOutput schema / properties / failures / description

Previous value: -"Sections that could not be created, with the reason for each. A failure here does not affect the other sections in the batch — do not retry the whole batch; address or drop the failed items."New value: +"Sections that could not be created, with the reason for each."

removedOutput schema / properties / successCount / description

Removed value: -"The number of successfully created sections."

removedOutput schema / properties / totalRequested / description
```
Removed value: -"The total number of sections requested."
```

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"

Changed7 schema fields changedv12.5.3Aug 7, 2026
- removedOutput schema / properties / failures / items / properties / code / description
```
Removed value: -"The error code, if available."
```
- removedOutput schema / properties / failures / items / properties / error / description
```
Removed value: -"The error message."
```
- changedOutput schema / properties / failures / items / properties / item / description
```
Previous value: -"The item that failed (usually an ID or identifier)."New value: +"Usually the ID of the item that failed."
```
- changedOutput schema / properties / sections / items / properties / description / description
```
Previous value: -"The description of the section. Supports Markdown."New value: +"Supports Markdown."
```
- removedOutput schema / properties / sections / items / properties / id / description
```
Removed value: -"The unique ID of the section."
```
- removedOutput schema / properties / sections / items / properties / name / description
```
Removed value: -"The name of the section."
```
- changedOutput schema / properties / sections / items / properties / sectionOrder / description
```
Previous value: -"The ordering index of the section within its project."New value: +"Ordering index within the project."
```

Changed5 schema fields changedv12.2.4Aug 3, 2026

addedOutput schema / properties / failureCount

Added value: +{
+  "description": "The number of failed section creations.",
+  "type": "number"
+}

addedOutput schema / properties / failures

Added value: +{
+  "description": "Sections that could not be created, with the reason for each. A failure here does not affect the other sections in the batch — do not retry the whole batch; address or drop the failed items.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "description": "The error code, if available.",
+        "type": "string"
+      },
+      "error": {
+        "description": "The error message.",
+        "type": "string"
+      },
+      "item": {
+        "description": "The item that failed (usually an ID or identifier).",
+        "type": "string"
+      }
+    },
+    "required": [
+      "item",
+      "error"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / successCount

Added value: +{
+  "description": "The number of successfully created sections.",
+  "type": "number"
+}

addedOutput schema / properties / totalRequested

Added value: +{
+  "description": "The total number of sections requested.",
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "sections",
-  "totalCount"
-]New value: +[
+  "sections",
+  "totalCount",
+  "failures",
+  "totalRequested",
+  "successCount",
+  "failureCount"
+]

Changed2 schema fields changedv12.1.2Jul 27, 2026

addedOutput schema / properties / sections / items / properties / sectionOrder

Added value: +{
+  "description": "The ordering index of the section within its project.",
+  "type": "number"
+}

changedOutput schema / properties / sections / items / required

Previous value: -[
-  "id",
-  "name"
-]New value: +[
+  "id",
+  "name",
+  "sectionOrder"
+]

First observedv10.4.2Jul 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what happens on duplicate section names (relevant given idempotentHint=false), whether the batch is atomic, or whether permissions are required.

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?

A single front-loaded sentence with zero filler. It is arguably too terse for the tool's complexity, but that gap is captured under contextual completeness rather than counted as verbosity here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema and rich annotations reduce the burden, and the schema fully documents the single nested parameter. Still missing is anything about duplicate handling, batch failure semantics, or ordering of created sections, which matters for a non-idempotent create tool.

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%, with nested field descriptions for name, projectId (including the 'inbox' sentinel) and description already documented. The description contributes no parameter meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Add ... new sections to projects') and makes the batch nature explicit with 'one or more.' It is distinguishable from update-sections/find-sections by convention, but the description never names them, so sibling differentiation is only implicit.

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

Usage Guidelines2/5

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

No when-to-use guidance, no exclusions, no mention of update-sections as the alternative for modifying existing sections. The only signal is the verb 'Add', which the agent must infer from the name.

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