Todoist AI MCP Server

Official

Overview Schema Related Servers Score Discussions

find-comments

Read-onlyIdempotent

Retrieve comments from a Todoist task or project, or fetch a specific comment by ID. Specify exactly one identifier to get the comments you need.

Instructions

Find comments by task, project, or get a specific comment by ID. Exactly one of taskId, projectId, or commentId must be provided.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of comments to return
`cursor`	No	Pagination cursor for retrieving more results.
`taskId`	No	Find comments for a specific task.
`commentId`	No	Get a specific comment by ID.
`projectId`	No	Find comments for a specific project. Project ID should be an ID string, or the text "inbox", for inbox tasks.

Output Schema

TableJSON Schema

Name	Required	Description
`hasMore`	Yes
`comments`	Yes	The found comments.
`searchId`	Yes	The ID that was searched for (comment, task, or project ID).
`nextCursor`	No
`searchType`	Yes	The type of search performed: "single" (comment ID), "task" (task ID), or "project" (project ID).
`totalCount`	Yes	The total number of comments in this page.

Schema Changelog

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

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"
+}

Changed21 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."
```
- 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."
```
First observedv10.4.2Jul 9, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The annotations (readOnlyHint, idempotentHint, destructiveHint) already convey the non-mutating nature. The description adds no extra side-effect information, but it does not contradict the annotations either. Given the annotations cover the key behavioral aspects, a score of 3 is appropriate.

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 a single, clear sentence that conveys all essential information without unnecessary elaboration. It is well-structured and easily parsed.

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?

The description covers the input requirements and the purpose. While it does not specify the return format, for a straightforward find operation this is not critical. The absence of output schema is not a major gap given the simplicity of the tool.

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?

The description adds the mutual exclusivity rule that is not evident from the schema alone, which is vital for correct usage. However, it does not elaborate beyond that; the schema descriptions for individual parameters are minimal, but the description compensates with the exclusivity constraint.

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 tool finds comments by task, project, or ID, and the verb 'find' specifies a read-only search operation. It distinguishes itself from sibling tools like find-tasks or find-projects by focusing specifically on comments.

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

Usage Guidelines4/5

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

The description explicitly states that exactly one of taskId, projectId, or commentId must be provided, which is a crucial usage constraint. While it does not explicitly contrast with alternatives, the tool's purpose is unambiguous for comment lookup scenarios.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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