Skip to main content
Glama
Sign In
Todoist MCP Server

Todoist MCP Server

by greirson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

todoist_tasks_bulk_create

Create multiple tasks simultaneously with support for due dates, priorities, labels, and duration for time blocking.

Instructions

Create multiple tasks at once for improved efficiency. Each task can have full attributes including duration for time blocking.

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": {
      "tasks": "<tasks>"
    },
    "name": "todoist_tasks_bulk_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksYesArray of task objects to create

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.3
    • addedInput schema / properties / tasks / items / properties / duration
      Added value: +{
+  "description": "Task duration amount for time blocking (e.g., 30 for 30 minutes). REQUIRES due_string with a time (optional)",
+  "type": "number"
+}
    • addedInput schema / properties / tasks / items / properties / duration_unit
      Added value: +{
+  "description": "Duration unit: 'minute' or 'day'. Defaults to 'minute'. Requires due_string with a time (optional)",
+  "enum": [
+    "minute",
+    "day"
+  ],
+  "type": "string"
+}
  2. Addedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'create multiple tasks' without details on mutation, authorization, limits, error handling, or atomicity. This is insufficient for a bulk creation 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 two sentences long, front-loaded with the core purpose, and contains no unnecessary words. Every sentence adds value.

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?

Given the complexity of bulk creation and the lack of annotations/output schema, the description is too sparse. It does not mention limits, partial failures, return value, or prerequisites. More context is needed for an AI agent to use it correctly.

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%, so the schema adequately describes all parameters. The description adds the note about 'duration for time blocking', but this is already covered in the schema. No additional meaning beyond what the schema provides.

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 tool's purpose: 'Create multiple tasks at once' with the verb 'create' and resource 'multiple tasks'. It emphasizes efficiency and mentions support for full attributes including duration, distinguishing it from single task creation and other bulk operations.

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 usage for efficiency but lacks explicit guidance on when to use this tool versus alternatives like todoist_task_create for single tasks or todoist_tasks_bulk_update for updates. No when-not-to-use or alternative tools are mentioned.

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