Skip to main content
Glama

list_next_actions

Retrieve all next actions from Todoist tasks using the (##Next actions | ##Brian acknowledged) & !subtask filter. Returns structured JSON data with task details including content, priority, due dates, and completion status.

Instructions

List all next actions from Todoist using the (##Next actions | ##Brian acknowledged) & !subtask filter. Returns structured JSON data with task details including id, content, description, completion status, labels, priority, due date, and comment count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler implementation for 'list_next_actions'. It calls the helper function listNextActions() and returns the result as formatted JSON text content.
    export const listNextActionsTool: Tool = {
      schema: {
        name: 'list_next_actions',
        description:
          'List all next actions from Todoist using the (##Next actions | ##Brian acknowledged) & !subtask filter. Returns structured JSON data with task details including id, content, description, completion status, labels, priority, due date, and comment count.',
        inputSchema: {
          type: 'object',
          properties: {},
          required: [],
        },
      },
      handler: async () => {
        console.error('Executing list_next_actions...');
        const result = await listNextActions();
        console.error('list_next_actions completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      },
    };
  • The schema definition for the 'list_next_actions' tool, specifying name, description, and empty input schema.
    schema: {
      name: 'list_next_actions',
      description:
        'List all next actions from Todoist using the (##Next actions | ##Brian acknowledged) & !subtask filter. Returns structured JSON data with task details including id, content, description, completion status, labels, priority, due date, and comment count.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • The core helper function that fetches next actions tasks from Todoist using the specified filter and transforms them into structured response.
    export async function listNextActions(): Promise<TasksResponse> {
      return await fetchTasksByFilter(
        '(##Next actions | ##Brian acknowledged) & !subtask',
        'list next actions'
      );
    }
  • Registration of the list_next_actions tool handler in the toolsWithoutArgs registry used by handleToolRequest.
    const toolsWithoutArgs: Record<string, () => Promise<ToolResponse>> = {
      list_personal_inbox_tasks: listPersonalInboxTasksTool.handler,
      list_brian_inbox_per_becky_tasks: listBrianInboxPerBeckyTasksTool.handler,
      list_becky_inbox_per_brian_tasks: listBeckyInboxPerBrianTasksTool.handler,
      list_next_actions: listNextActionsTool.handler,
      get_brian_only_projects: getBrianOnlyProjectsTool.handler,
      get_brian_shared_projects: getBrianSharedProjectsTool.handler,
      get_becky_shared_projects: getBeckySharedProjectsTool.handler,
      get_inbox_projects: getInboxProjectsTool.handler,
      get_context_labels: getContextLabelsTool.handler,
      get_chores_due_today: getChoresDueTodayTool.handler,
      get_tasks_due_tomorrow: getTasksDueTomorrowTool.handler,
      get_tasks_due_this_week: getTasksDueThisWeekTool.handler,
      get_tickler_tasks: getTicklerTasksTool.handler,
      list_gtd_projects: listGtdProjectsTool.handler,
      get_waiting_tasks: getWaitingTasksTool.handler,
      get_recent_media: getRecentMediaTool.handler,
      get_areas_of_focus: getAreasOfFocusTool.handler,
      get_shopping_list: getShoppingListTool.handler,
      list_brian_time_sensitive_tasks: listBrianTimeSensitiveTasksTool.handler,
      list_becky_time_sensitive_tasks: listBeckyTimeSensitiveTasksTool.handler,
    };
  • src/index.ts:85-86 (registration)
    Registration of the tool schema in the MCP server's listTools response.
    listBeckyInboxPerBrianTasksTool.schema,
    listNextActionsTool.schema,
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the filter behavior and return format (structured JSON with specific fields), which is valuable. However, it doesn't mention authentication needs, rate limits, error conditions, or whether this is a read-only operation (though 'List' implies safe read). More behavioral context would improve this for a tool with zero annotation coverage.

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 in two sentences: the first states the action and filter, the second details the return format. Every element earns its place—no redundant information, well front-loaded with the core purpose. It's appropriately sized for a no-parameter listing tool.

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?

Given the tool's complexity (simple listing with predefined filter), zero parameters, no annotations, and no output schema, the description provides good completeness. It explains the filter logic and return data structure, which compensates for the lack of output schema. However, for a tool with no annotations, adding brief safety/authentication context would make it fully complete.

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 input schema has 0 parameters with 100% coverage, so the schema already fully documents the lack of parameters. The description appropriately doesn't add parameter information beyond what's in the schema, maintaining focus on the tool's purpose and behavior. For zero-parameter tools, a baseline of 4 is appropriate when the description doesn't incorrectly suggest parameters.

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 ('List all next actions from Todoist') and resource ('next actions'), with precise filtering criteria ('(##Next actions | ##Brian acknowledged) & !subtask filter'). It distinguishes from siblings by focusing on a specific GTD workflow subset, unlike general task listing tools like 'get_tasks_due_this_week' or 'search_tasks'.

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 implies usage context through the specific filter criteria, suggesting this tool is for retrieving GTD-style next actions (excluding subtasks). However, it doesn't explicitly state when to use this versus alternatives like 'get_waiting_tasks' or 'list_brian_time_sensitive_tasks', nor does it provide exclusion guidance for other sibling tools.

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

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