Skip to main content
Glama
Doist

Todoist AI MCP Server

Official
by Doist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update-sections

Destructive

Update existing sections by providing new names or descriptions to modify multiple sections at once, keeping your Todoist projects organized.

Instructions

Update multiple existing sections with new values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionsYesThe sections to update.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionsYesThe updated sections.
totalCountYesThe total number of sections updated.
updatedSectionIdsYesThe IDs of the updated sections.

Schema Changelog

Changes observed during successful MCP inspections.

  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. Changed4 schema fields changedv12.5.3
    • 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. 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"
+]
  4. First observedv10.4.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already flag this as destructive, so the description does not need to repeat that. It adds the batching and scope idea ('multiple existing sections'), but it does not disclose what happens for nonexistent IDs, partial failures, or whether omitted optional fields are preserved or cleared.

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?

The description is a single front-loaded sentence with no filler. The phrase 'new values' is slightly generic, but overall the description is appropriately concise for the tool's simple parameter shape.

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 batch mutation tool, this is only minimally complete: the schema covers the inputs and the annotation covers destructiveness, but the description does not clarify what happens if one of the section ids is invalid or whether omitted fields are left unchanged. This is important context for a destructive batch operation.

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 input schema already explains the sections array, id, name, and description clearing semantics. The description adds little param-level value 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?

The description names a specific verb ('Update') and a specific resource ('existing sections'), and it conveys the batch nature ('multiple'). This clearly differentiates it from sibling tools such as add-sections and find-sections.

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?

It implies the tool should be used to modify existing sections, but it does not explicitly state when not to use it or mention alternatives like add-sections for creation or find-sections for discovery. The usage guidance is therefore only implicit.

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

Deploy Server

Other Tools