Skip to main content
Glama
Sign In
Todoist MCP Server

Todoist MCP Server

by greirson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

todoist_comment_get

Retrieve comments for a specific task or project in Todoist using its ID or name.

Instructions

Get comments for a task or project in Todoist

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "todoist_comment_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNoID of the task to get comments for (optional)
task_nameNoName/content of the task to get comments for (optional)
project_idNoID of the project to get comments for (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description fails to disclose behavior beyond the basic action. It does not mention output format, pagination, permissions, or rate limits, leaving the agent without key behavioral context.

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?

The description is very short (6 words) and front-loaded. It conveys the core purpose without excess, though it could benefit from slightly more detail without becoming verbose.

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 lack of an output schema and the presence of three optional parameters, the description should specify that at least one identifier is required and indicate the nature of the returned data. Currently, it is too sparse.

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 baseline is 3. The tool description adds no extra meaning beyond what the schema already provides for the three optional parameters.

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 verb ('Get') and resource ('comments'), and specifies that it can be for a task or project, which distinguishes it from sibling tools like todoist_comment_create or todoist_comment_delete.

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

Usage Guidelines3/5

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

The description does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites like providing at least one identifier. Usage is implied by the tool type.

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

Deploy Server

Other Tools