Skip to main content
Glama

list_personal_inbox_tasks

Retrieve all personal inbox tasks from Todoist with details like content, priority, due dates, and completion status. Use this tool to view and manage your pending tasks in a structured format.

Instructions

List all personal inbox tasks from Todoist using the ##Inbox 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

  • Tool definition including schema and handler. The handler executes the tool logic by calling the listPersonalInboxTasks service function and returning the result as JSON text.
    export const listPersonalInboxTasksTool: Tool = {
      schema: {
        name: 'list_personal_inbox_tasks',
        description:
          'List all personal inbox tasks from Todoist using the ##Inbox 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_personal_inbox_tasks...');
        const result = await listPersonalInboxTasks();
        console.error('list_personal_inbox_tasks completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      },
    };
  • Core helper function that fetches and transforms personal inbox tasks from Todoist using the Inbox project filter.
    export async function listPersonalInboxTasks(): Promise<TasksResponse> {
      return await fetchTasksByFilter(
        `##${ProjectNames.INBOX} & !subtask`,
        'list personal inbox tasks'
      );
    }
  • Registration of the tool's handler in the toolsWithoutArgs registry for dispatching tool calls.
    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:79-117 (registration)
    Registration of the tool's schema in the ListTools response for tool discovery.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          getTaskCommentsTool.schema,
          listPersonalInboxTasksTool.schema,
          listBrianInboxPerBeckyTasksTool.schema,
          listBeckyInboxPerBrianTasksTool.schema,
          listNextActionsTool.schema,
          getBrianOnlyProjectsTool.schema,
          getBrianSharedProjectsTool.schema,
          getBeckySharedProjectsTool.schema,
          getInboxProjectsTool.schema,
          createProjectLabelTool.schema,
          createTaskCommentTool.schema,
          updateTaskTool.schema,
          createTaskTool.schema,
          moveTaskTool.schema,
          getContextLabelsTool.schema,
          getTasksWithLabelTool.schema,
          completeTaskTool.schema,
          uncompleteTaskTool.schema,
          searchTasksTool.schema,
          searchTasksUsingAndTool.schema,
          searchTasksUsingOrTool.schema,
          getChoresDueTodayTool.schema,
          getTasksDueTomorrowTool.schema,
          getTasksDueThisWeekTool.schema,
          getTicklerTasksTool.schema,
          listGtdProjectsTool.schema,
          getWaitingTasksTool.schema,
          getRecentMediaTool.schema,
          getAreasOfFocusTool.schema,
          getShoppingListTool.schema,
          completeBeckyTaskTool.schema,
          listBrianTimeSensitiveTasksTool.schema,
          listBeckyTimeSensitiveTasksTool.schema,
        ],
      };
    });
  • Tool schema defining name, description, and empty input schema.
    schema: {
      name: 'list_personal_inbox_tasks',
      description:
        'List all personal inbox tasks from Todoist using the ##Inbox 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: [],
      },
    },
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns structured JSON data with specific task details, which is useful behavioral information. However, it does not mention potential limitations like rate limits, authentication requirements, pagination, or error handling, leaving gaps for a tool with no 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 a single, well-structured sentence that efficiently communicates the tool's purpose, source, filter, and output format. Every element adds value without redundancy, making it front-loaded and easy to parse.

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 low complexity (0 parameters, no output schema, no annotations), the description is reasonably complete. It explains what the tool does and what data it returns. However, without annotations or output schema, it could benefit from more behavioral details like error cases or data freshness, slightly limiting completeness.

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 no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose and output. This aligns with the baseline expectation for zero-parameter tools.

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 personal inbox tasks'), identifies the resource ('from Todoist'), and specifies the scope ('using the ##Inbox filter'). It distinguishes itself from siblings like 'list_becky_inbox_per_brian_tasks' by focusing on personal inbox tasks without user-specific qualifiers.

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 by specifying 'personal inbox tasks' and '##Inbox filter', which suggests this tool is for retrieving tasks from a specific Todoist view. However, it does not explicitly state when to use this tool versus alternatives like 'get_tasks_due_tomorrow' or 'search_tasks', nor does it provide exclusions or prerequisites.

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