Skip to main content
Glama

get_tasks_list

Retrieve tasks from Todoist with filtering options for projects, sections, labels, or custom queries to manage your to-do list.

Instructions

Get tasks list from Todoist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoFilter by project
section_idNoFilter by section
labelNoFilter by label
filterNoNatural language english filter like "search: keyword", "today", "date before: +4 hours", "date after: May 5", "no date", "no time", "overdue", "7 days & @waiting", "created before: -365 days", "assigned to: person", "added by: me", "#Project & !assigned", "subtask", "!subtask", "P1 | P2", "today & @email", "@work | @office", "(today | overdue) & #Work", "all & 7 days", "!assigned", "Today & !#Work"
idsNoComma-separated list of task IDs
limitNo

Implementation Reference

  • Registration and schema definition for the 'get_tasks_list' tool, specifying input parameters for filtering Todoist tasks and mapping to GET /tasks API endpoint.
    createApiHandler({
        name: 'get_tasks_list',
        description: 'Get tasks list from Todoist',
        schemaShape: {
            project_id: z.string().optional().describe('Filter by project'),
            section_id: z.string().optional().describe('Filter by section'),
            label: z.string().optional().describe('Filter by label'),
            filter: z
                .string()
                .optional()
                .describe(
                    'Natural language english filter like "search: keyword", "today", "date before: +4 hours", "date after: May 5", "no date", "no time", "overdue", "7 days & @waiting", "created before: -365 days", "assigned to: person", "added by: me", "#Project & !assigned", "subtask", "!subtask", "P1 | P2", "today & @email", "@work | @office", "(today | overdue) & #Work", "all & 7 days", "!assigned", "Today & !#Work"'
                ),
            ids: z.string().optional().describe('Comma-separated list of task IDs'),
            limit: z.number().optional().default(50),
        },
        method: 'GET',
        path: '/tasks',
    });
  • Core handler logic for API-based tools like get_tasks_list: processes arguments into path and query params, validates path parameters, and calls todoistApi.get('/tasks', finalParams) for GET requests.
    const handler = async (args: z.infer<z.ZodObject<T>>): Promise<R> => {
        let finalPath = options.path;
        const pathParams: Record<string, string> = {};
    
        // Extract path parameters (e.g., {id}) and replace them with actual values
        const pathParamRegex = /{([^}]+)}/g;
        let match;
    
        while ((match = pathParamRegex.exec(options.path)) !== null) {
            const fullMatch = match[0]; // e.g., "{id}"
            const paramName = match[1]; // e.g., "id"
    
            if (args[paramName] === undefined) {
                throw new Error(`Path parameter ${paramName} is required but not provided`);
            }
    
            // Validate and encode path parameter using the centralized security function
            const safeParamValue = validatePathParameter(args[paramName], paramName);
            finalPath = finalPath.replace(fullMatch, safeParamValue);
            pathParams[paramName] = String(args[paramName]);
        }
    
        // Collect non-path parameters for query string or request body
        const otherParams = Object.entries(args).reduce(
            (acc, [key, value]) => {
                if (value !== undefined && !pathParams[key]) {
                    acc[key] = value;
                }
                return acc;
            },
            {} as Record<string, any>
        );
    
        // Apply custom parameter transformation if provided
        const finalParams = options.transformParams ? options.transformParams(args) : otherParams;
    
        // Execute the API request based on HTTP method
        let result;
        switch (options.method) {
            case 'GET':
                result = await todoistApi.get(finalPath, finalParams);
                break;
            case 'POST':
                log('POST', finalPath, finalParams);
                result = await todoistApi.post(finalPath, finalParams);
                break;
            case 'DELETE':
                result = await todoistApi.delete(finalPath);
                break;
        }
    
        // Apply result post-processing if provided
        return options.processResult ? options.processResult(result, args) : result;
    };
  • TodoistClient.get method that executes the HTTP GET request to Todoist REST API /tasks endpoint with query parameters, handling auth and response.
    async get(endpoint: string, params: Record<string, string> = {}): Promise<any> {
        let url = `${API_BASE_URL}${endpoint}`;
    
        const queryParams = new URLSearchParams();
        for (const [key, value] of Object.entries(params)) {
            if (value) {
                queryParams.append(key, value);
            }
        }
    
        const queryString = queryParams.toString();
        if (queryString) {
            url += `?${queryString}`;
        }
    
        log(`Making GET request to: ${url}`);
    
        const response = await fetch(url, {
            method: 'GET',
            headers: this.getHeaders(),
        });
    
        return this.handleResponse(response);
    }
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 but only states the basic action. It doesn't mention whether this is a read-only operation, what permissions are required, how results are returned (pagination, format), rate limits, or any other behavioral characteristics beyond the minimal 'get' operation.

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 extremely concise at just 5 words, front-loading the essential information with zero wasted words. It efficiently communicates the core purpose without unnecessary elaboration.

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 6 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what kind of list is returned, how results are structured, whether there's pagination, or any behavioral context. The minimal description fails to compensate for the lack of structured metadata.

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?

With 83% schema description coverage, the schema already documents most parameters well, especially the 'filter' parameter with extensive examples. The description adds no parameter information beyond what's in the schema, so it meets the baseline expectation but doesn't enhance understanding of parameter usage or interactions.

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 ('tasks list from Todoist'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'get_tasks' or 'get_completed_tasks', which would require more specific scope information.

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. With sibling tools like 'get_tasks' and 'get_completed_tasks' available, there's no indication of how this list retrieval differs from those other retrieval operations or when one should be preferred over another.

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

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