Skip to main content
Glama
Sign In
Todoist MCP Server

Todoist MCP Server

by greirson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

todoist_project_get

Retrieve your Todoist projects with IDs, names, descriptions, and hierarchy to manage tasks.

Instructions

Get a list of all projects from Todoist with their IDs, names, descriptions, and hierarchy information

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It indicates a read-only operation and lists returned fields, but does not mention authentication, permissions, error conditions, or any limitations. Adequate but not thorough.

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 sentence, direct and to the point. Every word adds value, with no redundancy or extraneous information.

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?

Given no output schema, the description explains return fields sufficiently. It lacks details on pagination, error handling, or performance, but for a simple parameterless list tool, it covers the essentials.

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 input schema has no parameters, so the description does not need to add meaning. It clarifies that the tool returns all projects without filtering, which is implicit but enough. Baseline for 0 params is 4.

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 action (get a list), the resource (all projects), and the return fields (IDs, names, descriptions, hierarchy information). It distinguishes itself from sibling tools that deal with activities, backups, comments, etc.

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 implies basic usage, but there is no explicit guidance on when to use this tool versus alternatives like todoist_archived_projects_get or todoist_project_get for a specific project. No comparison or context is provided.

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