Todoist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

update-comments

Destructive

Update multiple existing Todoist comments with new content in a single operation. Modify comment text by ID to keep task discussions current.

Instructions

Update multiple existing comments with new content.

Input Schema

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

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv13.8.0Oct 29, 2026

addedOutput schema / properties / appliedOperations / properties / failureCount
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / properties / appliedOperations / required

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

addedOutput schema / properties / failures

Added value: +{
+  "description": "Comments that could not be updated, with the reason for each.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "error": {
+        "type": "string"
+      },
+      "item": {
+        "description": "Usually the ID of the item that failed.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "item",
+      "error"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "comments",
-  "totalCount",
-  "updatedCommentIds",
-  "appliedOperations"
-]New value: +[
+  "comments",
+  "totalCount",
+  "updatedCommentIds",
+  "failures",
+  "appliedOperations"
+]

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"

Changed1 schema field changedv12.6.0Aug 19, 2026

addedOutput schema / properties / comments / items / properties / notifiedUserIds

Added value: +{
+  "description": "Users notified about this comment. Absent when nobody was notified.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed19 schema fields changedv12.5.3Aug 7, 2026
- removedOutput schema / properties / comments / items / properties / content / description
```
Removed value: -"The content of the comment."
```
- removedOutput schema / properties / comments / items / properties / fileAttachment / description
```
Removed value: -"File attachment information, if any."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / fileDuration / description
```
Previous value: -"The duration in milliseconds (for audio/video files)."New value: +"Milliseconds, for audio/video."
```
- removedOutput schema / properties / comments / items / properties / fileAttachment / properties / fileName / description
```
Removed value: -"The name of the file."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / fileSize / description
```
Previous value: -"The size of the file in bytes."New value: +"Bytes."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / fileType / description
```
Previous value: -"The MIME type of the file."New value: +"MIME type."
```
- removedOutput schema / properties / comments / items / properties / fileAttachment / properties / fileUrl / description
```
Removed value: -"The URL to access the file."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / image / description
```
Previous value: -"The image URL for image resource types."New value: +"For image resource types."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / imageHeight / description
```
Previous value: -"The height of the image in pixels."New value: +"Pixels."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / imageWidth / description
```
Previous value: -"The width of the image in pixels."New value: +"Pixels."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / resourceType / description
```
Previous value: -"The type of resource (file, url, image, etc)."New value: +"file, url, image, etc."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / title / description
```
Previous value: -"The title for link/url resource types."New value: +"For link/url resource types."
```
- removedOutput schema / properties / comments / items / properties / fileAttachment / properties / uploadState / description
```
Removed value: -"The upload state of the file."
```
- changedOutput schema / properties / comments / items / properties / fileAttachment / properties / url / description
```
Previous value: -"The URL for link/url resource types."New value: +"For link/url resource types."
```
- removedOutput schema / properties / comments / items / properties / id / description
```
Removed value: -"The unique ID of the comment."
```
- changedOutput schema / properties / comments / items / properties / postedAt / description
```
Previous value: -"When the comment was posted (ISO 8601 format)."New value: +"ISO 8601."
```
- removedOutput schema / properties / comments / items / properties / postedUid / description
```
Removed value: -"The UID of the user who posted this comment."
```
- removedOutput schema / properties / comments / items / properties / projectId / description
```
Removed value: -"The ID of the project this comment belongs to."
```
- removedOutput schema / properties / comments / items / properties / taskId / description
```
Removed value: -"The ID of the task this comment belongs to."
```
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 destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description only adds the 'multiple/batch' nuance; it does not disclose permission requirements, whether only the caller's own comments can be edited, or failure behavior when some IDs are invalid.

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 efficient sentence with the verb and scope front-loaded. Nothing is wasted, though there is little structure to speak of.

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 batch mutation, the description omits the constraints an agent needs: whose comments can be edited, what happens on partial failure, and per-comment error handling. The output schema and annotations help, but the gaps around mutation semantics remain.

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% and the nested id/content structure is fully documented there. The description's 'multiple existing comments' hints at the array shape and the requirement that comments pre-exist, but adds nothing about the id/content semantics beyond the schema.

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 ('update ... comments') plus batch scope ('multiple existing comments'). It is clear what the tool does, but it does not differentiate itself from siblings like add-comments or delete-object.

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?

There is no guidance on when to use this versus add-comments (create) or find-comments (read), nor any mention of prerequisites such as needing to be the comment's author.

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