Skip to main content
Glama
greirson

Todoist MCP Server

todoist_section_update

Update a Todoist section's name using its section ID or search by section name. Specify a project to narrow the search.

Instructions

Update an existing section in Todoist. Can update name by section ID or section name search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
section_idNoSection ID to update (takes precedence over section_name if both provided)
section_nameNoSection name to search for (case-insensitive partial match)
project_idNoProject ID to narrow down section search when using section_name
nameNoNew name for the section
Behavior2/5

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

With no annotations, the description must detail behavioral traits. It only states 'update' without mentioning side effects, return values, idempotency, or permission requirements. Minimal transparency.

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?

Two concise sentences with no unnecessary words. Front-loaded with primary purpose and method. Efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and the description does not explain what the tool returns (e.g., updated section object or status). Lacks details on success/rejection indicators and prerequisites for invocation.

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 has 100% coverage, so baseline 3. The description adds little beyond what's in the schema descriptions (e.g., precedence logic already documented). Meets minimum but does not exceed.

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?

Clearly states the action (update), resource (section), and primary field (name). Distinguishes from sibling tools like section_create, section_delete, etc. The description is specific and unambiguous.

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?

No guidance on when to use this tool versus alternatives (e.g., section_archive, section_move). Does not provide context for selection among sibling section tools.

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/greirson/mcp-todoist'

If you have feedback or need assistance with the MCP directory API, please join our Discord server