Enhanced Todoist MCP Server Extended

todoist_create_comment

Add comments to Todoist tasks or projects to provide context, share updates, or attach files for better collaboration and task clarity.

Instructions

Create a new comment on a task or project

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>"
    },
    "name": "todoist_create_comment"
  }
}

Input Schema

Name	Required	Description
`content`	Yes	The content/text of the comment
`taskId`	No	Task ID to add comment to (provide either taskId or projectId, not both)
`projectId`	No	Project ID to add comment to (provide either taskId or projectId, not both)
`attachment`	No	Optional file attachment (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 12, 2025

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool creates a comment, implying a write/mutation operation, but doesn't cover permissions, rate limits, side effects (e.g., notifications), or response format. This is a significant gap for a mutation tool with zero annotation coverage.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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?

Given the complexity (mutation tool with 4 parameters and nested objects), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like permissions or side effects, nor does it explain return values or error conditions, leaving critical gaps for agent usage.

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 schema already documents all parameters (content, taskId, projectId, attachment) with clear descriptions. The description adds no additional parameter semantics beyond what's in the schema, but the baseline is 3 when schema coverage is high.

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?

The description clearly states the action ('Create a new comment') and the target resources ('on a task or project'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like todoist_update_comment or todoist_delete_comment, though the verb 'Create' implies distinction from update/delete operations.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing task/project), exclusions, or comparisons to related tools like todoist_update_comment or todoist_get_comments, leaving the agent without contextual usage cues.

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