Skip to main content
Glama
Sign In
Doist

Todoist AI MCP Server

Official
by Doist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update-filters

Destructive

Modify existing personal Todoist filters by updating names, colors, queries, favorites, and descriptions in a single request.

Instructions

Update one or more existing personal filters with new values.

Input Schema

NameRequiredDescriptionDefault
filtersYesThe filters to update.

Output Schema

NameRequiredDescriptionDefault
filtersYesThe updated filters, as read back after the update. Empty if they could not be read back; updatedFilterIds still lists what was updated.
failuresYesFilters that could not be updated, with the reason for each.
totalCountYesThe total number of filters updated.
updatedFilterIdsYesThe IDs of the updated filters.
appliedOperationsYesSummary of operations performed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv13.8.4
    • changedInput schema / properties / filters / items / required
      Previous value: -[
-  "id",
-  "color"
-]New value: +[
+  "id"
+]
  2. Changed5 schema fields changedv13.8.0
    • addedOutput schema / properties / appliedOperations / properties / failureCount
      Added value: +{
+  "type": "number"
+}
    • changedOutput schema / properties / appliedOperations / required
      Previous value: -[
-  "updateCount",
-  "skippedCount"
-]New value: +[
+  "updateCount",
+  "skippedCount",
+  "failureCount"
+]
    • addedOutput schema / properties / failures
      Added value: +{
+  "description": "Filters that could not be updated, 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 / properties / filters / description
      Previous value: -"The updated filters."New value: +"The updated filters, as read back after the update. Empty if they could not be read back; updatedFilterIds still lists what was updated."
    • changedOutput schema / required
      Previous value: -[
-  "filters",
-  "totalCount",
-  "updatedFilterIds",
-  "appliedOperations"
-]New value: +[
+  "filters",
+  "totalCount",
+  "updatedFilterIds",
+  "failures",
+  "appliedOperations"
+]
  3. Changed2 schema fields changedv13.2.1
    • addedInput schema / properties / filters / items / properties / description
      Added value: +{
+  "description": "A markdown description explaining what the filter is for. Use \"remove\" to clear the description; omit the field to leave it unchanged.",
+  "type": "string"
+}
    • addedOutput schema / properties / filters / items / properties / description
      Added value: +{
+  "description": "A markdown description explaining what the filter is for. Omitted when the filter has none.",
+  "type": "string"
+}
  4. 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"
  5. Changed1 schema field changedv12.5.3
    • removedOutput schema / properties / filters / items / properties / color / description
      Removed value: -"The color key of the entity."
  6. First observedv10.4.2

TDQS

B3.3/5.0
Behavior2/5

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

The description is purely functional and adds no unique behavioral traits. The primary behavioral constraints (e.g., destructive nature, mutability) are already defined by the annotations (destructiveHint: true, readOnlyHint: false).

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 tool is described in one extremely concise sentence. Every word serves to define the scope of the operation without superfluous detail.

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?

Despite the complex input structure (nested array of objects with many attributes), the description remains high-level. While the schema handles the heavy lifting, a slightly more descriptive summary of the update operation's impact would improve completeness.

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 coverage is 100%, meaning the description does not need to compensate for missing parameter explanations. Since it provides no additional semantic context beyond the schema, the baseline score of 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?

The description clearly identifies the resource (filters) and the action (update). It is distinct from 'add-filters' and 'find-filters' in the sibling list. It uses a specific action/resource pairing.

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 necessity of existing filters, but provides no explicit advice on whether to first call 'find-filters' or if there are specific conditions (like minimum required fields) for success, making the guidance slightly weak.

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