Todoist MCP Server

import-project-template

Import tasks, sections, and comments into an existing Todoist project using a template ID, URL, or CSV content.

Instructions

Import a template into an existing project, adding its tasks, sections and comments to whatever is already there. Source it by template ID/URL or by passing CSV content from export-project-template. To start a new project from a template, create the project with add-projects first, then import into it. This writes immediately and cannot be undone, so only run it against a project the user named.

Input Schema

TableJSON Schema

Name	Required	Description
`locale`	No	Locale for the imported content when using `templateId`. Defaults to "en".
`projectId`	Yes	The ID of the existing project to import the template into.
`templateId`	No	The template to import — either a gallery slug ("product-launch"), a personal template ID ("UT_28Ex..."), or a full Todoist template URL, which is reduced to the ID automatically. Gallery templates work for anyone; personal templates only for the account that owns them. There is no way to list templates through this server, so only use the ID or URL the user supplied. Provide either this or `csvFileContent`, not both.
`csvFileContent`	No	Raw CSV template content, as produced by export-project-template. Provide either this or `templateId`, not both.

Output Schema

TableJSON Schema

Name	Required	Description
`tasks`	Yes	Tasks created by the import.
`comments`	Yes	Comments created by the import.
`sections`	Yes	Sections created by the import.
`totalCount`	Yes	The total number of objects created by the import.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv13.3.1Sep 22, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds important non-obvious behavior beyond the annotations: writes immediately, cannot be undone, and merges into existing project content. It also clarifies template source limitations (gallery vs. personal templates). This does not contradict destructiveHint=false because the operation adds rather than destroys existing data, though it is irreversible.

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?

Three sentences, each earning its place: the primary behavior, the sourcing options, and the new-project workflow plus safety warning. The most important information is front-loaded before the cautionary guidance.

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

Completeness5/5

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

Provides the essential context for a mutating import operation: merge semantics, source options, workflow for new projects, and irreversibility. Since an output schema exists, the description doesn't need to explain return values, and nothing critical for correct invocation is missing.

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 input schema already documents projectId, templateId, csvFileContent, and locale thoroughly. The description repeats the ID/URL/CSV distinction and the mutual exclusivity, but adds little meaning beyond what the schema already provides.

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?

States a specific verb ('import') with a clear resource (template) and target (existing project), and explains the merge semantics by listing what gets added: tasks, sections, and comments. It distinguishes itself from siblings like export-project-template and add-projects by focusing on importing into an existing project.

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

Usage Guidelines5/5

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

Explicitly names the workflow for new projects: create the project with add-projects first, then import. It also tells the agent when to use template ID/URL versus CSV content from export-project-template, and warns to only run it against a project the user named.

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