Skip to main content
Glama

list_becky_inbox_per_brian_tasks

Retrieve tasks assigned to Brian from Becky's Todoist inbox. Returns structured JSON with task details including content, priority, due dates, and completion status.

Instructions

List all Becky inbox per Brian tasks from Todoist using the ##Becky inbox - per Brian 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 helper function and formatting the response as MCP content.
    export const listBeckyInboxPerBrianTasksTool: Tool = {
      schema: {
        name: 'list_becky_inbox_per_brian_tasks',
        description:
          'List all Becky inbox per Brian tasks from Todoist using the ##Becky inbox - per Brian 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_becky_inbox_per_brian_tasks...');
        const result = await listBeckyInboxPerBrianTasks();
        console.error('list_becky_inbox_per_brian_tasks completed successfully');
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      },
    };
  • Helper function that performs the actual Todoist query for Becky inbox per Brian tasks using the specific filter.
    export async function listBeckyInboxPerBrianTasks(): Promise<TasksResponse> {
      return await fetchTasksByFilter(
        `##${ProjectNames.BECKY_INBOX_PER_BRIAN} & !subtask`,
        'list Becky inbox per Brian tasks'
      );
    }
  • Registers the tool's handler function in the toolsWithoutArgs registry map, mapping the tool name to its handler for execution.
    list_becky_inbox_per_brian_tasks: listBeckyInboxPerBrianTasksTool.handler,
  • src/index.ts:85-85 (registration)
    Registers the tool's schema in the list of tools provided to the MCP server for tool discovery.
    listBeckyInboxPerBrianTasksTool.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 return format ('structured JSON data') and enumerates the data fields included, which is valuable behavioral information. However, it doesn't mention potential limitations like pagination, rate limits, authentication requirements, or error conditions.

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: one stating the action and source, another detailing the return format. Every element serves a purpose with no redundant information, making it easy to parse and understand quickly.

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 read-only listing tool with no parameters and no output schema, the description provides good coverage: it specifies the exact data source, filter criteria, and return data structure. The main gap is lack of information about potential constraints (pagination, rate limits) that would be helpful for an agent.

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 tool has 0 parameters with 100% schema description coverage. The description appropriately doesn't discuss parameters since none exist, and instead focuses on what the tool does and returns. This meets the baseline expectation for parameterless 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 Becky inbox per Brian tasks'), source system ('from Todoist'), and filter criteria ('using the ##Becky inbox - per Brian filter'). It distinguishes itself from sibling tools like 'list_brian_inbox_per_becky_tasks' by specifying the exact user perspective and filter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by mentioning the specific filter, but doesn't explicitly state when to use this tool versus alternatives like 'list_personal_inbox_tasks' or 'get_tasks_with_label'. It provides some guidance through the filter specification but lacks explicit comparison or exclusion statements.

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