Skip to main content
Glama
Doist

Todoist AI MCP Server

Official
by Doist
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

add-sections

Add multiple sections to any Todoist project by providing names and project IDs, with optional markdown descriptions.

Instructions

Add one or more new sections to projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionsYesThe array of sections to add.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
failuresYesSections that could not be created, with the reason for each. A failure here does not affect the other sections in the batch — do not retry the whole batch; address or drop the failed items.
sectionsYesThe created sections.
totalCountYesThe total number of sections created.
failureCountYesThe number of failed section creations.
successCountYesThe number of successfully created sections.
totalRequestedYesThe total number of sections requested.

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. Changed7 schema fields changedv12.5.3
    • removedOutput schema / properties / failures / items / properties / code / description
      Removed value: -"The error code, if available."
    • removedOutput schema / properties / failures / items / properties / error / description
      Removed value: -"The error message."
    • changedOutput schema / properties / failures / items / properties / item / description
      Previous value: -"The item that failed (usually an ID or identifier)."New value: +"Usually the ID of the item that failed."
    • changedOutput schema / properties / sections / items / properties / description / description
      Previous value: -"The description of the section. Supports Markdown."New value: +"Supports Markdown."
    • removedOutput schema / properties / sections / items / properties / id / description
      Removed value: -"The unique ID of the section."
    • removedOutput schema / properties / sections / items / properties / name / description
      Removed value: -"The name of the section."
    • changedOutput schema / properties / sections / items / properties / sectionOrder / description
      Previous value: -"The ordering index of the section within its project."New value: +"Ordering index within the project."
  3. Changed5 schema fields changedv12.2.4
    • addedOutput schema / properties / failureCount
      Added value: +{
+  "description": "The number of failed section creations.",
+  "type": "number"
+}
    • addedOutput schema / properties / failures
      Added value: +{
+  "description": "Sections that could not be created, with the reason for each. A failure here does not affect the other sections in the batch — do not retry the whole batch; address or drop the failed items.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "description": "The error code, if available.",
+        "type": "string"
+      },
+      "error": {
+        "description": "The error message.",
+        "type": "string"
+      },
+      "item": {
+        "description": "The item that failed (usually an ID or identifier).",
+        "type": "string"
+      }
+    },
+    "required": [
+      "item",
+      "error"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / successCount
      Added value: +{
+  "description": "The number of successfully created sections.",
+  "type": "number"
+}
    • addedOutput schema / properties / totalRequested
      Added value: +{
+  "description": "The total number of sections requested.",
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "sections",
-  "totalCount"
-]New value: +[
+  "sections",
+  "totalCount",
+  "failures",
+  "totalRequested",
+  "successCount",
+  "failureCount"
+]
  4. Changed2 schema fields changedv12.1.2
    • addedOutput schema / properties / sections / items / properties / sectionOrder
      Added value: +{
+  "description": "The ordering index of the section within its project.",
+  "type": "number"
+}
    • changedOutput schema / properties / sections / items / required
      Previous value: -[
-  "id",
-  "name"
-]New value: +[
+  "id",
+  "name",
+  "sectionOrder"
+]
  5. First observedv10.4.2

TDQS

B3.3/5.0
Behavior3/5

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

The description is transparent that this creates new non-read-only sections, and annotations already flag readOnlyHint=false, destructiveHint=false, and idempotentHint=false. However, it adds little beyond that, omitting potential duplicate handling, batch behavior, or failure semantics.

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?

The description is a single front-loaded sentence with no filler. Every word contributes to stating the operation and target resource.

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 simple create tool with full schema coverage and an output schema, the description is minimally viable. It lacks usage alternatives and behavioral nuance, but the schema covers the single parameter adequately.

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 parameter meaning is fully handled by the input schema. The description adds no extra semantic detail beyond the schema, which is acceptable but not value-adding.

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 states a specific action ('Add') and resource ('new sections to projects'), making the tool's purpose clear. It implicitly differentiates from update-sections by using 'new sections', but does not explicitly name any alternative.

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?

The description gives no guidance on when to prefer this tool over alternatives like find-sections or update-sections, nor does it mention prerequisites or exclusions. Usage is only implied by the verb 'Add'.

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