Skip to main content
Glama
Sign In
Todoist MCP Server

Todoist MCP Server

by abhiz123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

todoist_create_task

Create a new task in Todoist by specifying content, optional due date, priority, and description using natural language.

Instructions

Create a new task in Todoist with optional description, due date, and priority

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": {
      "content": "<content>"
    },
    "name": "todoist_create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesThe content/title of the task
priorityNoTask priority from 1 (normal) to 4 (urgent) (optional)
due_stringNoNatural language due date like 'tomorrow', 'next Monday', 'Jan 23' (optional)
descriptionNoDetailed description of the task (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It lacks disclosure of side effects, return values, or error conditions. Only states basic creation with optional fields.

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?

Single sentence, 15 words, no redundancy. Core action and resource are front-loaded. Every word adds value, and the structure is 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?

Given the complexity (4 parameters, no output schema, no annotations), the description lacks completeness. It does not mention what the tool returns on success, error handling, or prerequisites for use.

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 description coverage is 100%, so the baseline is 3. The description adds minimal value by restating that fields are optional, which is already clear from the schema. No additional semantics 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 specifies the action 'Create' and the resource 'task in Todoist', and lists optional fields. It distinguishes the tool from siblings like update, delete, complete, and get by focusing on creation.

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. No prerequisites or context provided, leaving the agent to infer based solely on the tool name and sibling list.

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