Skip to main content
Glama

create_task

Add new tasks to Todoist with content, due dates, priorities, and labels to organize your workflow.

Instructions

Create a new task in Todoist.

Priorities don't map directly to Todoist priorities, but are mapped as follows:
1 = low
2 = medium
3 = high
4 = urgent

This is done to map better to how people think about priorities.

Args:
    content: The task content/title (required)
    description: Task description (optional)
    project_name: Project name to add task to
    due_string: Due date in natural language like "tomorrow", "next monday" (optional)
    priority: Priority level 1-4 (1=low, 2=medium, 3=high, 4=urgent)
    labels: List of label names to add to the task (optional)

Returns:
    Dict containing the created task details or error message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
descriptionNo
project_nameNo
due_stringNo
priorityNo
labelsNo
Behavior4/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 clearly indicates this is a write operation ('Create'), explains the priority mapping system in detail, and mentions the return format ('Dict containing the created task details or error message'). However, it doesn't address authentication requirements, rate limits, or what happens with invalid inputs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (purpose, priority mapping, args, returns) and every sentence adds value. The priority mapping explanation is necessary but slightly lengthy. Overall efficient with minimal waste, though could be slightly more concise in the priority explanation.

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

Completeness4/5

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

For a creation tool with no annotations and no output schema, the description provides substantial context: clear purpose, detailed parameter semantics, return format indication, and priority system explanation. The main gaps are lack of error handling details and authentication context, but overall it's quite complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing detailed semantic explanations for all 6 parameters. Each parameter gets clear explanations of purpose, optionality, format expectations (e.g., 'natural language like "tomorrow"'), and the priority mapping table adds crucial context not inferable from the schema alone.

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 specific action ('Create a new task') and resource ('in Todoist'), distinguishing it from sibling tools like list_active_tasks and list_completed_tasks which are read operations rather than creation operations. The verb+resource combination is precise 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context through the parameter explanations (e.g., 'optional' flags), but doesn't explicitly state when to use this tool versus alternatives. No guidance is provided about prerequisites, error conditions, or comparison with sibling tools beyond their different functions.

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

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