Todoist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

project-move

DestructiveIdempotent

Moves a Todoist project between personal and workspace contexts, optionally assigning it to a workspace folder or setting visibility for team access.

Instructions

Move a project between personal and workspace contexts.

Input Schema

Name	Required	Description
`action`	Yes	The action to perform on the project.
`folderId`	No	Optional target folder ID within the workspace.
`projectId`	Yes	The ID of the project to move.
`visibility`	No	Optional access visibility for the project in the workspace (restricted, team, or public).
`workspaceId`	No	The target workspace ID. Required when action is move-to-workspace.

Output Schema

Name	Required	Description	Default
`project`	Yes	The moved project.
`success`	Yes	Whether the move was successful.

Schema Changelog

Changes observed during successful MCP inspections.

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"

Changed13 schema fields changedv12.5.3Aug 7, 2026
- changedOutput schema / properties / project / properties / childOrder / description
```
Previous value: -"The ordering index of the project among its siblings."New value: +"Ordering index among siblings."
```
- removedOutput schema / properties / project / properties / color / description
```
Removed value: -"The color key of the entity."
```
- changedOutput schema / properties / project / properties / description / description
```
Previous value: -"The description of the project (empty string if none)."New value: +"Empty string when none."
```
- changedOutput schema / properties / project / properties / folderId / description
```
Previous value: -"The ID of the folder this project belongs to (workspace projects only)."New value: +"Workspace projects only."
```
- removedOutput schema / properties / project / properties / id / description
```
Removed value: -"The unique ID of the project."
```
- removedOutput schema / properties / project / properties / inboxProject / description
```
Removed value: -"Whether this is the inbox project."
```
- removedOutput schema / properties / project / properties / isArchived / description
```
Removed value: -"Whether the project is archived."
```
- removedOutput schema / properties / project / properties / isFavorite / description
```
Removed value: -"Whether the project is marked as favorite."
```
- removedOutput schema / properties / project / properties / isShared / description
```
Removed value: -"Whether the project is shared."
```
- removedOutput schema / properties / project / properties / name / description
```
Removed value: -"The name of the project."
```
- removedOutput schema / properties / project / properties / parentId / description
```
Removed value: -"The ID of the parent project (for sub-projects)."
```
- changedOutput schema / properties / project / properties / viewStyle / description
```
Previous value: -"The view style of the project (list, board, calendar)."New value: +"list, board or calendar."
```
- changedOutput schema / properties / project / properties / workspaceId / description
```
Previous value: -"The ID of the workspace this project belongs to (undefined for personal projects)."New value: +"Undefined for personal projects."
```
First observedv10.4.2Jul 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already carry the full safety profile (destructiveHint=true, idempotentHint=true, openWorldHint=false), but the description adds nothing on top. For a destructive cross-context move, it says nothing about what is destroyed or altered — e.g. whether collaborators, folder placement, or visibility are reset — which is exactly the context an agent needs before calling it.

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?

A single efficient sentence with the core operation front-loaded and no filler. It is arguably too thin rather than too long, but there is zero waste.

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?

An output schema exists, so return values need not be explained, but for a 5-parameter destructive mutation the description omits the side effects of moving a project across contexts. An agent would have to consult the schema and guess at consequences.

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 all five parameters including the enums and the conditional workspaceId are documented in the schema. The description adds no syntax or conditional logic beyond that, so the baseline 3 applies.

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 has a specific verb ("Move") and resource ("project") plus the axis of movement (personal <-> workspace), so the operation is unambiguous. It does not differentiate itself from siblings like update-projects or project-management, which could plausibly overlap with this change.

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?

There is no guidance on when to choose this tool versus update-projects or project-management, and no mention of the required action enum or the conditional workspaceId requirement. The agent must infer all preconditions from the schema.

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