Skip to main content
Glama
Doist

Todoist AI MCP Server

Official
by Doist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update-filters

Destructive

Update existing Todoist personal filters by changing their name, color, query, favorite status, or description.

Instructions

Update one or more existing personal filters with new values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersYesThe filters to update.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersYesThe updated filters.
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. 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"
+}
  2. 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"
  3. Changed1 schema field changedv12.5.3
    • removedOutput schema / properties / filters / items / properties / color / description
      Removed value: -"The color key of the entity."
  4. First observedv10.4.2

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already indicate destructiveHint: true and readOnlyHint: false, so the description does not need to restate that. However, it adds no extra behavioral detail beyond the implied mutation of filters, such as whether updates are partial or require all fields, or what happens to unspecified properties.

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, concise sentence that directly conveys the tool's purpose without redundant wording. It is front-loaded with the action and subject, making it easy to parse and understand at a glance.

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 mutating operation, the description covers the fundamental action but omits contextual details such as the output/response format (despite an output schema being present) and potential error conditions (e.g., nonexistent filter IDs). While annotations convey destructive nature, the lack of information about results or edge cases leaves the agent somewhat underinformed.

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?

The input schema provides thorough descriptions for the single 'filters' parameter and each nested property (id, color, query, etc.), covering 100% of the schema. The tool description itself adds no additional semantic meaning beyond what the schema already offers, so it relies on the schema's detail.

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 clearly states a specific action ('Update') on a distinct resource ('existing personal filters') and indicates the operation modifies with 'new values.' It differentiates itself from sibling tools like add-filters and find-filters by explicitly targeting existing filters for modification.

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 does not provide any guidance on when to use this tool versus alternatives. It lacks explicit mention of scenarios where updating is appropriate or when other operations like adding or finding filters would be preferred, leaving usage decisions to the agent's inference.

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