Todoist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

update-projects

Destructive

Batch update multiple existing Todoist projects to change names, colors, view styles, favorite status, or descriptions, keeping your project list current.

Instructions

Update multiple existing projects with new values.

Input Schema

Name	Required	Description	Default
`projects`	Yes	The projects to update.

Output Schema

Name	Required	Description
`failures`	Yes	Projects that could not be updated, with the reason for each.
`projects`	Yes	The updated projects.
`totalCount`	Yes	The total number of projects updated.
`appliedOperations`	Yes	Summary of operations performed.
`updatedProjectIds`	Yes	The IDs of the updated projects.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv13.8.4Nov 2, 2026
- changedInput schema / properties / projects / items / required
```
Previous value: -[
-  "id",
-  "color"
-]New value: +[
+  "id"
+]
```

Changed2 schema fields changedv13.8.0Oct 29, 2026

removedOutput schema / properties / appliedOperations / properties / failureCount / description
```
Removed value: -"The number of projects that failed to update."
```

changedOutput schema / properties / failures / description

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

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"

Changed16 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 / projects / items / properties / childOrder / description
```
Previous value: -"The ordering index of the project among its siblings."New value: +"Ordering index among siblings."
```
- removedOutput schema / properties / projects / items / properties / color / description
```
Removed value: -"The color key of the entity."
```
- changedOutput schema / properties / projects / items / properties / description / description
```
Previous value: -"The description of the project (empty string if none)."New value: +"Empty string when none."
```
- changedOutput schema / properties / projects / items / properties / folderId / description
```
Previous value: -"The ID of the folder this project belongs to (workspace projects only)."New value: +"Workspace projects only."
```
- removedOutput schema / properties / projects / items / properties / id / description
```
Removed value: -"The unique ID of the project."
```
- removedOutput schema / properties / projects / items / properties / inboxProject / description
```
Removed value: -"Whether this is the inbox project."
```
- removedOutput schema / properties / projects / items / properties / isArchived / description
```
Removed value: -"Whether the project is archived."
```
- removedOutput schema / properties / projects / items / properties / isFavorite / description
```
Removed value: -"Whether the project is marked as favorite."
```
- removedOutput schema / properties / projects / items / properties / isShared / description
```
Removed value: -"Whether the project is shared."
```
- removedOutput schema / properties / projects / items / properties / name / description
```
Removed value: -"The name of the project."
```
- removedOutput schema / properties / projects / items / properties / parentId / description
```
Removed value: -"The ID of the parent project (for sub-projects)."
```
- changedOutput schema / properties / projects / items / properties / viewStyle / description
```
Previous value: -"The view style of the project (list, board, calendar)."New value: +"list, board or calendar."
```
- changedOutput schema / properties / projects / items / properties / workspaceId / description
```
Previous value: -"The ID of the workspace this project belongs to (undefined for personal projects)."New value: +"Undefined for personal projects."
```

Changed4 schema fields changedv12.2.4Aug 3, 2026

addedOutput schema / properties / appliedOperations / properties / failureCount

Added value: +{
+  "description": "The number of projects that failed to update.",
+  "type": "number"
+}

changedOutput schema / properties / appliedOperations / required

Previous value: -[
-  "updateCount",
-  "skippedCount"
-]New value: +[
+  "updateCount",
+  "skippedCount",
+  "failureCount"
+]

addedOutput schema / properties / failures

Added value: +{
+  "description": "Projects that could not be updated, with the reason for each. A failure here does not affect the other projects 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"
+}

changedOutput schema / required

Previous value: -[
-  "projects",
-  "totalCount",
-  "updatedProjectIds",
-  "appliedOperations"
-]New value: +[
+  "projects",
+  "totalCount",
+  "updatedProjectIds",
+  "failures",
+  "appliedOperations"
+]

First observedv10.4.2Jul 9, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is known from structured data; the description adds nothing beyond that. It does not warn that updates overwrite existing field values, that passing description clears it, or that color fallback to charcoal can silently change data — all relevant given the destructive flag.

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

Conciseness3/5

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

A single front-loaded sentence with no waste, but it is under-specified rather than efficient — 'with new values' is vague filler that conveys no actionable information.

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

Completeness2/5

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

For a destructive, non-idempotent batch mutation with an output schema present, the description should at minimum note that callers must supply the project id and that unspecified fields are left untouched (or not). Return values needn't be explained given the output schema, but the mutation semantics gap is a real omission.

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 nested project fields, enum values, and the 'null/empty string clears description' behavior are already documented in the schema. The description only reinforces the batch/array nature ('multiple existing projects'), which is the baseline expectation when the schema does the heavy lifting.

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 (update) plus resource (projects) and clarifies the batch semantics ('multiple existing projects'), which separates it from add-projects and find-projects. It doesn't name any sibling explicitly, but the resource name is distinctive enough within the sibling set.

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 prerequisites, and no mention of alternatives such as project-management or add-projects for creation. The agent must infer from the name alone that this mutates existing projects rather than creating or reorganizing them.

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