Skip to main content
Glama
Doist

Todoist AI MCP Server

Official
by Doist
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

project-move

Idempotent

Move a Todoist project between personal and workspace contexts. Specify the project ID and the target action (move-to-workspace or move-to-personal) to relocate it.

Instructions

Move a project between personal and workspace contexts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe action to perform on the project.
folderIdNoOptional target folder ID within the workspace.
projectIdYesThe ID of the project to move.
visibilityNoOptional access visibility for the project in the workspace (restricted, team, or public).
workspaceIdNoThe target workspace ID. Required when action is move-to-workspace.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe moved project.
successYesWhether the move was successful.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv13.0.0
    • 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"
  2. Changed13 schema fields changedv12.5.3
    • 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."
  3. First observedv10.4.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, and idempotent. The description adds the context transition (personal vs workspace) but no further behavioral details such as permission requirements, visibility implications, or side effects on collaboration. It does not contradict annotations.

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?

A single, front-loaded sentence conveys the core purpose with no redundancy. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter tool with conditional requirements (workspaceId needed for move-to-workspace), the description is minimal. It does not explain the move's impact or preconditions, though the schema covers parameter semantics. With an output schema present, return values aren't needed, but the behavioral implications of moving remain under-specified.

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 fully documents all parameters. The description itself adds no parameter-specific meaning beyond the schema, thus meeting the baseline but not exceeding it.

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 uses a specific verb ('Move') and resource ('project') and clearly scopes the operation to between personal and workspace contexts. This distinguishes it from sibling tools like add-projects, update-projects, or find-projects.

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 the use case (relocating a project between contexts) but does not explicitly state when to use this tool versus alternatives like update-projects or project-management. No exclusions or alternative references are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Doist/todoist-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server