Skip to main content
Glama

todoist_list_tasks

Read-onlyIdempotent

Retrieve tasks from Todoist using filters like project, label, due date, or priority to organize and manage your to-do list.

Instructions

List tasks from Todoist with optional filters.

Supports filtering by project, label, or using Todoist's filter syntax.
Common filters: 'today', 'tomorrow', 'overdue', 'p1', 'p2', 'no due date',
'due before: tomorrow', '7 days', '@label_name', '#project_name'.

Args:
    params: ListTasksInput containing:
        - project_id: Filter by project
        - label: Filter by label name
        - filter: Todoist filter query
        - limit: Maximum tasks to return
        - response_format: 'markdown' or 'json'

Returns:
    List of tasks with their content, due dates, and priorities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=true, covering safety and idempotency. The description adds value by specifying the return format options ('markdown' or 'json') and listing common filter examples, which provides practical behavioral context beyond the annotations.

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 efficiently structured: a clear purpose statement, filter support explanation with examples, and a well-organized Args/Returns section. Every sentence adds value without redundancy, making it easy to parse.

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

Completeness5/5

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

Given the tool's moderate complexity (filtering capabilities), rich annotations, and the presence of an output schema, the description is complete. It covers purpose, parameters, usage examples, and return information, providing all necessary context for an agent to use the tool effectively.

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

Parameters4/5

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

With 0% schema description coverage, the schema provides no parameter descriptions. The description compensates well by listing all parameters (project_id, label, filter, limit, response_format) with brief explanations and examples, adding significant meaning beyond the bare 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 verb ('List') and resource ('tasks from Todoist'), and specifies the optional filtering capability. It distinguishes this tool from siblings like todoist_get_task (single task) and todoist_complete_task (mutation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description provides clear context about when to use this tool ('List tasks... with optional filters') and offers examples of common filters. However, it doesn't explicitly state when NOT to use it or mention specific alternatives among the siblings, such as using todoist_get_task for a single task.

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

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