Skip to main content
Glama
Sign In
Doist

Todoist AI MCP Server

Official
by Doist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update-labels

Destructive

Modify existing Todoist labels: rename personal labels and change color, order, or favorite status; rename shared labels across tasks.

Instructions

Update one or more existing labels. Personal labels (identified by ID) can have their name, color, order, and favorite flag updated. Shared labels (identified by name) can only be renamed.

Input Schema

NameRequiredDescriptionDefault
labelsYesThe labels to update. Use labelType="personal" with an ID to update a personal label, or labelType="shared" with name+newName to rename a shared label.

Output Schema

NameRequiredDescriptionDefault
failuresYesLabels that could not be updated, identified by ID (personal) or name (shared), with the reason for each.
totalCountYesThe total number of successful operations (personal + shared).
updatedLabelsYesThe updated personal labels.
appliedOperationsYesSummary of operations performed.
renamedSharedLabelsYesThe shared labels that were renamed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv13.8.4
    • changedInput schema / properties / labels / items / oneOf
      Previous value: -[
-  {
-    "properties": {
-      "color": {
-        "description": "Color for the entity. Accepts a color key (e.g. \"berry_red\") or display name (e.g. \"Berry Red\"). Valid colors: berry_red, red, orange, yellow, olive_green, lime_green, green, mint_green, teal, sky_blue, light_blue, blue, grape, violet, lavender, magenta, salmon, charcoal, grey, taupe. Unrecognized colors are omitted and charcoal will be used as the default.",
-        "enum": [
-          "berry_red",
-          "red",
-          "orange",
-          "yellow",
-          "olive_green",
-          "lime_green",
-          "green",
-          "mint_green",
-          "teal",
-          "sky_blue",
-          "light_blue",
-          "blue",
-          "grape",
-          "violet",
-          "lavender",
-          "magenta",
-          "salmon",
-          "charcoal",
-          "grey",
-          "taupe"
-        ],
-        "type": "string"
-      },
-      "id": {
-        "description": "The ID of the personal label to update.",
-        "minLength": 1,
-        "type": "string"
-      },
-      "isFavorite": {
-        "description": "Whether to mark the label as a favorite.",
-        "type": "boolean"
-      },
-      "labelType": {
-        "const": "personal",
-        "description": "Update a personal label, identified by its ID.",
-        "type": "string"
-      },
-      "name": {
-        "description": "The new name of the label.",
-        "maxLength": 128,
-        "minLength": 1,
-        "type": "string"
-      },
-      "order": {
-        "description": "The new position of the label in the label list.",
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "labelType",
-      "id",
-      "color"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "labelType": {
-        "const": "shared",
-        "description": "Rename a shared label across all tasks. Shared labels are identified by name; only renaming is supported (no color, order, or favorite).",
-        "type": "string"
-      },
-      "name": {
-        "description": "The current name of the shared label.",
-        "minLength": 1,
-        "type": "string"
-      },
-      "newName": {
-        "description": "The new name for the shared label.",
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "labelType",
-      "name",
-      "newName"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "color": {
+        "description": "Color for the entity. Accepts a color key (e.g. \"berry_red\") or display name (e.g. \"Berry Red\"). Valid colors: berry_red, red, orange, yellow, olive_green, lime_green, green, mint_green, teal, sky_blue, light_blue, blue, grape, violet, lavender, magenta, salmon, charcoal, grey, taupe. Unrecognized colors are omitted and charcoal will be used as the default.",
+        "enum": [
+          "berry_red",
+          "red",
+          "orange",
+          "yellow",
+          "olive_green",
+          "lime_green",
+          "green",
+          "mint_green",
+          "teal",
+          "sky_blue",
+          "light_blue",
+          "blue",
+          "grape",
+          "violet",
+          "lavender",
+          "magenta",
+          "salmon",
+          "charcoal",
+          "grey",
+          "taupe"
+        ],
+        "type": "string"
+      },
+      "id": {
+        "description": "The ID of the personal label to update.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "isFavorite": {
+        "description": "Whether to mark the label as a favorite.",
+        "type": "boolean"
+      },
+      "labelType": {
+        "const": "personal",
+        "description": "Update a personal label, identified by its ID.",
+        "type": "string"
+      },
+      "name": {
+        "description": "The new name of the label.",
+        "maxLength": 128,
+        "minLength": 1,
+        "type": "string"
+      },
+      "order": {
+        "description": "The new position of the label in the label list.",
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "labelType",
+      "id"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "labelType": {
+        "const": "shared",
+        "description": "Rename a shared label across all tasks. Shared labels are identified by name; only renaming is supported (no color, order, or favorite).",
+        "type": "string"
+      },
+      "name": {
+        "description": "The current name of the shared label.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "newName": {
+        "description": "The new name for the shared label.",
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "labelType",
+      "name",
+      "newName"
+    ],
+    "type": "object"
+  }
+]
  2. Changed4 schema fields changedv13.8.0
    • addedOutput schema / properties / appliedOperations / properties / failureCount
      Added value: +{
+  "type": "number"
+}
    • changedOutput schema / properties / appliedOperations / required
      Previous value: -[
-  "updateCount",
-  "renameCount",
-  "skippedCount"
-]New value: +[
+  "updateCount",
+  "renameCount",
+  "skippedCount",
+  "failureCount"
+]
    • addedOutput schema / properties / failures
      Added value: +{
+  "description": "Labels that could not be updated, identified by ID (personal) or name (shared), with the reason for each.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "error": {
+        "type": "string"
+      },
+      "item": {
+        "description": "Usually the ID of the item that failed.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "item",
+      "error"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "updatedLabels",
-  "renamedSharedLabels",
-  "totalCount",
-  "appliedOperations"
-]New value: +[
+  "updatedLabels",
+  "renamedSharedLabels",
+  "totalCount",
+  "failures",
+  "appliedOperations"
+]
  3. 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"
  4. Changed5 schema fields changedv12.5.3
    • removedOutput schema / properties / updatedLabels / items / properties / color / description
      Removed value: -"The color key of the entity."
    • removedOutput schema / properties / updatedLabels / items / properties / id / description
      Removed value: -"The unique ID of the label."
    • removedOutput schema / properties / updatedLabels / items / properties / isFavorite / description
      Removed value: -"Whether the label is marked as favorite."
    • removedOutput schema / properties / updatedLabels / items / properties / name / description
      Removed value: -"The name of the label."
    • changedOutput schema / properties / updatedLabels / items / properties / order / description
      Previous value: -"The display order of the label."New value: +"Display order."
  5. First observedv10.4.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false. The description adds genuinely useful mode-level semantics (shared rename vs. personal full-field update), but it does not warn that shared-label renames propagate to all tasks, nor does it acknowledge that the operation is destructive or non-idempotent. It adds value beyond annotations without fully carrying the behavioral burden.

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?

Two sentences, front-loaded with the core action and then the mode breakdown. Nearly every clause earns its place, though the parenthetical '(identified by ID)' / '(identified by name)' duplicates the schema's discriminators.

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?

Output schema exists and annotations cover the safety profile, so the description only needs to explain the two update modes, which it does completely and accurately. Missing is any mention of how to discover IDs or that updates apply per-label in a batch, but the essentials for a correct call are present.

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 nested oneOf already documents both branches in detail, including the shared-label rename note. The description restates that branch split at a higher level, which aids quick parsing but adds no syntax or constraint information the schema lacks. Baseline 3 is appropriate.

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?

Names a specific verb (update) and resource (labels), and immediately splits the operation into two distinct modes: personal labels by ID and shared labels by name. An agent can tell this apart from add-labels or find-labels from the name and description alone, though the description never names those siblings to reinforce the boundary.

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?

Implies 'use this to modify existing labels rather than create them', but never states preconditions such as needing an existing label ID (from find-labels) or the fact that shared labels must already exist. There is no explicit when-not guidance and no reference to alternatives like add-labels for creation.

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