Skip to main content
Glama
Sign In
Todoist MCP Server

Todoist MCP Server

by greirson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

todoist_project_create

Create a new project in Todoist with optional sub-project hierarchy, description, color, favorite, and view style settings.

Instructions

Create a new project in Todoist with optional sub-project hierarchy, description, and view style

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": {
      "name": "<name>"
    },
    "name": "todoist_project_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the project
colorNoColor for the project (optional). Valid colors: berry_red, red, orange, yellow, olive_green, lime_green, green, mint_green, teal, sky_blue, light_blue, blue, grape, violet, lavender, magenta, salmon, charcoal, grey, taupe
is_favoriteNoWhether to mark the project as favorite (optional)
parent_idNoParent project ID to create this as a sub-project (optional). Creates a hierarchical relationship.
descriptionNoDescription of the project (optional)
view_styleNoView style for the project (optional). Options: 'list' (default) or 'board' (kanban-style)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.3
    • changedInput schema / properties / color / description
      Previous value: -"Color for the project (optional)"New value: +"Color for the project (optional). Valid colors: berry_red, red, orange, yellow, olive_green, lime_green, green, mint_green, teal, sky_blue, light_blue, blue, grape, violet, lavender, magenta, salmon, charcoal, grey, taupe"
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Description of the project (optional)",
+  "type": "string"
+}
    • addedInput schema / properties / parent_id
      Added value: +{
+  "description": "Parent project ID to create this as a sub-project (optional). Creates a hierarchical relationship.",
+  "type": "string"
+}
    • addedInput schema / properties / view_style
      Added value: +{
+  "description": "View style for the project (optional). Options: 'list' (default) or 'board' (kanban-style)",
+  "type": "string"
+}
  2. Addedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It does not mention the return value, error handling, authentication requirements, or effects like what happens if parent_id is invalid. For a mutation tool, this is insufficient.

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 a single efficient sentence that front-loads the key action. It is concise, though a slight improvement could be listing mandatory vs optional parameters.

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 tool has 6 parameters and no output schema or annotations, the description is too brief. It does not explain the full context of project creation, such as workspace scope, project nesting implications, or typical workflow.

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 coverage is 100%, so each parameter is already described in the schema. The description adds minimal value by summarizing optional features, but does not provide additional semantics beyond the schema.

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 'Create' and the resource 'project', and distinguishes from sibling tools by mentioning optional sub-project hierarchy, description, and view style. It effectively conveys the tool's primary function.

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?

No guidance is provided on when to use this tool versus alternatives like update, archive, or delete. The description lacks context about prerequisites or scenarios where creation is appropriate.

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