Skip to main content
Glama
Sign In
Todoist MCP Server

Todoist MCP Server

by greirson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

todoist_task_reorder

Assign a new position index to a task to reorder it within its project or section. Lower numbers appear first, enabling priority sorting.

Instructions

Set the order of a task within its project/section. Lower numbers appear first.

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": {
      "child_order": "<child_order>"
    },
    "name": "todoist_task_reorder"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNoThe ID of the task to reorder
task_nameNoThe name of the task to reorder (partial match, case-insensitive)
child_orderYesThe new position/order for the task (0-based index)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the effect (reordering) but does not disclose any potential side effects, failure modes, permission requirements, or whether the operation is reversible. For a simple mutation, this is adequate but minimal.

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?

One sentence of 11 words. Direct, efficient, and front-loaded with the action. No wasted words.

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?

Given 3 parameters and no output schema, the description is sparse. It does not mention what happens if the task is not found, what the response looks like, or any error conditions. For a simple operation it may be sufficient, but completeness is average.

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, so the baseline is 3. The description adds 'Lower numbers appear first' which clarifies the meaning of child_order. However, it does not explain how to identify the task (task_id vs task_name) beyond what the schema already provides. No extra semantic value beyond the schema.

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 the action: 'Set the order of a task within its project/section' and explains the meaning of the value ('Lower numbers appear first'). This distinguishes it from sibling tools like todoist_task_move (which moves to another project) and todoist_tasks_reorder_bulk (bulk operation).

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?

The description implies when to use it (to reorder a single task) but provides no explicit guidance on when not to use it vs alternatives like todoist_task_move, todoist_tasks_reorder_bulk, or todoist_task_day_order_update. There is no mention of prerequisites or conditions.

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