Skip to main content
Glama

list_brian_time_sensitive_tasks

Retrieve Brian's time-sensitive Todoist tasks filtered by ##Brian time sensitive (per BP) & !subtask criteria. Returns structured JSON with task details for priority management.

Instructions

List all Brian time sensitive tasks from Todoist using the ##Brian time sensitive \(per BP\) & !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

  • Defines the MCP tool 'list_brian_time_sensitive_tasks' including schema and handler. The handler fetches tasks via service and returns JSON-formatted response.
    export const listBrianTimeSensitiveTasksTool: Tool = {
      schema: {
        name: 'list_brian_time_sensitive_tasks',
        description: `List all Brian time sensitive tasks from Todoist using the ##${ProjectNames.BRIAN_TIME_SENSITIVE} & !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_brian_time_sensitive_tasks...');
        const result = await listBrianTimeSensitiveTasks();
        console.error('list_brian_time_sensitive_tasks completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      },
    };
  • Schema definition for the 'list_brian_time_sensitive_tasks' tool, specifying name, description, and empty input schema.
    schema: {
      name: 'list_brian_time_sensitive_tasks',
      description: `List all Brian time sensitive tasks from Todoist using the ##${ProjectNames.BRIAN_TIME_SENSITIVE} & !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: [],
      },
    },
  • Core helper function that fetches Brian time-sensitive tasks from Todoist using project filter excluding subtasks, via generic fetchTasksByFilter.
    export async function listBrianTimeSensitiveTasks(): Promise<TasksResponse> {
      return await fetchTasksByFilter(
        `##${ProjectNames.BRIAN_TIME_SENSITIVE} & !subtask`,
        'list Brian time sensitive tasks'
      );
    }
  • Registers the tool handler in toolsWithoutArgs registry for dispatching tool calls without arguments.
    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:113-114 (registration)
    Registers the tool schema in the MCP server's listTools response.
    listBrianTimeSensitiveTasksTool.schema,
    listBeckyTimeSensitiveTasksTool.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 that the tool returns structured JSON data with specific task details (e.g., id, content, due date), which is helpful behavioral context. However, it does not mention potential limitations like rate limits, authentication needs, or pagination behavior, leaving gaps for a read 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 a single, well-structured sentence that efficiently conveys the tool's purpose, filter criteria, and return format without any wasted words. It is front-loaded with the core action and resource, making it easy to understand at a glance.

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 (a read operation with no parameters) and lack of annotations or output schema, the description is mostly complete: it specifies the filter, data source (Todoist), and return details. However, it could improve by mentioning authentication or rate limits, but for a simple list tool, it provides sufficient context for effective use.

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, and the baseline score is 4 for zero parameters, as it avoids unnecessary information while clearly stating the tool's purpose and output.

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 action ('List all'), resource ('Brian time sensitive tasks from Todoist'), and scope ('using the ##Brian time sensitive (per BP) & !subtask filter'), distinguishing it from siblings like list_becky_time_sensitive_tasks and get_tasks_with_label. It specifies the exact filter criteria, making the purpose highly specific and unambiguous.

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 for retrieving Brian's time-sensitive tasks with a specific filter, but does not explicitly state when to use this tool versus alternatives like list_becky_time_sensitive_tasks or get_tasks_due_this_week. It provides clear context (Todoist, Brian, time-sensitive tasks) but lacks explicit exclusions or comparisons to 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