Enhanced Todoist MCP Server Extended

todoist_create_section

Create a new section within a Todoist project to organize tasks by category, phase, or priority. Specify the section name and project ID to structure your workflow.

Instructions

Create a new section in a project

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "projectId": "<projectId>"
    },
    "name": "todoist_create_section"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The name of the section
`projectId`	Yes	The project ID where the section will be created
`order`	No	Order of the section (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 12, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a section but doesn't mention any behavioral traits such as permissions required, whether it's idempotent, error conditions, or what happens on success (e.g., returns a section ID). This leaves significant gaps for a mutation tool.

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, efficient sentence that directly states the tool's purpose without any wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a section object or ID), error handling, or side effects, which are critical for an agent to use it correctly in a Todoist context.

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 has 100% description coverage, with clear documentation for all three parameters (name, projectId, order). The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline score of 3 for adequate but not enhanced parameter understanding.

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 states the action ('Create') and resource ('new section in a project'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'todoist_create_project' or 'todoist_create_task', which would require mentioning it's specifically for organizing tasks within projects rather than creating projects or tasks themselves.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing project), exclusions, or comparisons to siblings like 'todoist_update_section' or 'todoist_get_sections', leaving the agent to infer usage context solely from the tool name and schema.

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