Skip to main content
Glama

get-tasks

Retrieve all tasks from Todoist to view, organize, or manage your to-do list through the MCP Todoist server.

Instructions

Get all the tasks from Todoist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP protocol handler for 'todoist_get_tasks' tool. Dispatches to TodoistClient.getTasks with input arguments and returns the result as JSON-formatted text content.
    case 'todoist_get_tasks':
      const tasks = await this.todoistClient.getTasks(args)
      return this.createResponse(requestId, {
        content: [
          {
            type: 'text',
            text: JSON.stringify(tasks, null, 2)
          }
        ]
      })
  • Tool schema definition including input schema for parameters like project_id, filter, and limit. Used in tools/list response.
    {
      name: 'todoist_get_tasks',
      description: 'Get tasks from Todoist',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'Project ID to filter tasks' },
          filter: { type: 'string', description: 'Filter expression' },
          limit: { type: 'number', description: 'Maximum number of tasks to return' }
        }
      }
    },
  • Tool visibility configuration where todoist_get_tasks is set to true (enabled/registered for use). Controls which tools are exposed via tools/list.
    const TOOL_VISIBILITY = {
      todoist_get_tasks: true,
      todoist_create_task: true,
      todoist_update_task: true,
      todoist_close_task: true,
      todoist_get_projects: true,
      todoist_create_project: false,  // 非公開
      todoist_update_project: false,  // 非公開
      todoist_delete_project: false,  // 非公開
      todoist_move_task: true,
    } as const
  • Core implementation of getTasks in TodoistClient adapter. Makes authenticated GET request to Todoist API /tasks endpoint with optional params.
    async getTasks(params?: GetTasksParams): Promise<TodoistTask[]> {
      return this.makeRequest<TodoistTask[]>('GET', '/tasks', undefined, params);
    }
  • TypeScript interface defining input parameters for getTasks, matching the tool's inputSchema.
    export interface GetTasksParams {
      project_id?: string;
      section_id?: string;
      label?: string;
      filter?: string;
      lang?: string;
      ids?: number[];
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but provides no information about permissions required, rate limits, pagination behavior, or what format the returned tasks will have. 'Get all the tasks' implies a read operation but lacks critical behavioral details.

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 a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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?

For a tool with no annotations, no output schema, and no parameters, the description is insufficiently complete. It doesn't address what 'all the tasks' means in practice (active only? completed? archived?), doesn't mention authentication requirements, and provides no information about the return format or structure.

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?

The tool has zero parameters with 100% schema description coverage, so the schema fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, earning a baseline score of 4 for not introducing confusion about non-existent parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get') and resource ('all the tasks from Todoist'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'get-projects' or 'get-project-id', but the resource specificity (tasks vs projects) provides implicit differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get-projects' or 'add-task-to-project'. It doesn't mention prerequisites, limitations, or appropriate contexts for retrieving all tasks versus filtered subsets.

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

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