Skip to main content
Glama

get_tickler_tasks

Retrieve overdue and today's Todoist tasks labeled for tickler review, returning structured task details including due dates, priorities, and completion status.

Instructions

Get all tickler tasks that are due today or overdue from Todoist. Tickler tasks are tasks with labels #Tickler, #Ansonia Tickler, or #Brian tickler. 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 handler function for the 'get_tickler_tasks' tool. It calls getTicklerTasks(), stringifies the result to JSON, and returns it as MCP content.
    handler: async () => {
      console.error('Executing get_tickler_tasks...');
      const result = await getTicklerTasks();
      console.error('get_tickler_tasks completed successfully');
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    },
  • The schema definition for the 'get_tickler_tasks' tool, including name, description, and empty input schema.
    schema: {
      name: 'get_tickler_tasks',
      description:
        'Get all tickler tasks that are due today or overdue from Todoist. Tickler tasks are tasks with labels #Tickler, #Ansonia Tickler, or #Brian tickler. 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: [],
      },
    },
  • Registration of no-arg tools in toolsWithoutArgs map, dispatching 'get_tickler_tasks' to its handler.
    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,
    };
  • Helper function getTicklerTasks that queries Todoist API with filter for tickler tasks due today or overdue, used by the tool handler.
    export async function getTicklerTasks(): Promise<TodoistTask[]> {
      return await fetchRawTasksByFilter(
        '(today | overdue) & (#Tickler | #Ansonia Tickler | #Brian tickler)',
        'get tickler tasks'
      );
    }
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 of behavioral disclosure. It clearly describes what the tool returns ('structured JSON data with task details') and the specific label filtering logic, but doesn't mention potential limitations like rate limits, authentication requirements, or error conditions. It adequately covers the core behavior but lacks operational context.

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 purpose and filtering criteria, the second describes the return format. Every element earns its place with no redundant information, and key details are front-loaded.

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?

For a zero-parameter read-only tool with no output schema, the description provides good completeness: it explains what's retrieved, the filtering logic, and the return format. However, it doesn't specify whether results are paginated or limited, which could be relevant given Todoist's API constraints. The absence of annotations means some operational context is missing.

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 parameters and 100% schema description coverage, the baseline would be 4. The description appropriately explains that no parameters are needed while clarifying the implicit filtering logic (today/overdue tasks with specific labels), adding meaningful context beyond the empty 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 ('Get') and resource ('all tickler tasks'), specifies the source ('from Todoist'), defines what constitutes a tickler task ('tasks with labels #Tickler, #Ansonia Tickler, or #Brian tickler'), and distinguishes from siblings by focusing on overdue/today due tasks with specific labels rather than general task retrieval tools like get_tasks_due_today or get_tasks_with_label.

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 for when to use this tool ('tasks that are due today or overdue' with specific tickler labels), but doesn't explicitly state when NOT to use it or name specific alternatives among the many sibling tools. It implies usage for tickler-specific overdue tasks rather than general task queries.

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