Todoist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

export-project-template

Idempotent

Export a Todoist project as a reusable template in CSV or as a shareable URL, so you can duplicate its structure or share it. Dates can be relative to import time.

Instructions

Export an existing project as a Todoist template, either as CSV content or as a shareable URL. Use it to duplicate a project, share its structure, or hand the CSV to import-project-template. To read a project rather than export it, use find-tasks instead — it returns structured tasks rather than raw CSV. The project itself is not modified, but the "url" format uploads a copy and returns a link that anyone holding it can open.

Input Schema

Name	Required	Description	Default
`format`	No	How to return the template. "file" returns the CSV content, which can be passed straight back to import-project-template. "url" returns a shareable download link instead, and is the better choice for large projects because it does not return the whole file.	file
`projectId`	Yes	The ID of the project to export as a template.
`useRelativeDates`	No	Export due dates relative to the import date (e.g. "day 3") instead of absolute dates. Defaults to false.

Output Schema

Name	Required	Description
`format`	Yes	The format the template was exported in.
`content`	No	The template as CSV content. Only present when format is "file".
`fileUrl`	No	The shareable download URL. Only present when format is "url".
`fileName`	No	The generated template file name. Only present when format is "url".
`lineCount`	No	Number of rows in the exported CSV. Only present when format is "file".

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"

Addedv12.5.0Aug 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, so the safety profile is partially covered; the description adds the non-obvious facts that the source project is not modified and that the 'url' format uploads a copy returning a publicly openable link. This is real value beyond annotations, though permission requirements and size limits are left implicit (large-project guidance lives in the schema).

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 tight sentences, front-loaded with the action and its outputs, then use cases, then the sibling pointer, then the side-effect caveat. No repeated or filler content.

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?

With an output schema present, return values needn't be explained, and the description still covers formats, side effects, and the correct sibling for read-only needs. Minor gap: nothing about required permissions or workspace scope for the upload path, which matters for an open-world tool.

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% and the format enum is fully documented in the schema, including the large-project rationale. The description only echoes that two formats exist and says nothing about useRelativeDates, so it adds no semantics beyond the schema — baseline 3 applies.

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?

Opens with a specific verb+resource ('Export an existing project as a Todoist template') and immediately names the two output forms (CSV content or shareable URL). An agent can distinguish this from import-project-template and find-tasks without opening any schema.

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?

Gives concrete use cases (duplicate a project, share its structure, hand CSV to import-project-template) and an explicit exclusion: 'To read a project rather than export it, use find-tasks instead — it returns structured tasks rather than raw CSV.' Both when-to-use and the named alternative are present.

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