Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_quick_add_task

Create Todoist tasks using natural language input to quickly add tasks with due dates, projects, and labels through text parsing.

Instructions

Create a task using Todoist's Quick Add feature with natural language parsing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesNatural language text for quick task creation (e.g., 'Buy milk tomorrow at 2pm #shopping')
noteNoAdditional note for the task (optional)
reminderNoReminder time (optional)

Implementation Reference

  • Executes the tool by validating arguments with isQuickAddArgs and calling todoistClient.quickAddTask with the provided text, optional note, and reminder.
    if (name === "todoist_quick_add_task") {
      if (!isQuickAddArgs(args)) {
        throw new Error("Invalid arguments for todoist_quick_add_task");
      }
      
      const quickAddData: any = { text: args.text };
      if (args.note) quickAddData.note = args.note;
      if (args.reminder) quickAddData.reminder = args.reminder;
    
      const result = await todoistClient.quickAddTask(quickAddData);
      return {
        content: [{ 
          type: "text", 
          text: `Task created via Quick Add:\n${JSON.stringify(result, null, 2)}` 
        }],
        isError: false,
      };
    }
  • Tool definition including name, description, and JSON input schema specifying required 'text' and optional 'note' and 'reminder'.
    const QUICK_ADD_TASK_TOOL: Tool = {
      name: "todoist_quick_add_task",
      description: "Create a task using Todoist's Quick Add feature with natural language parsing",
      inputSchema: {
        type: "object",
        properties: {
          text: {
            type: "string",
            description: "Natural language text for quick task creation (e.g., 'Buy milk tomorrow at 2pm #shopping')"
          },
          note: {
            type: "string",
            description: "Additional note for the task (optional)"
          },
          reminder: {
            type: "string",
            description: "Reminder time (optional)"
          }
        },
        required: ["text"]
      }
    };
  • src/index.ts:1083-1121 (registration)
    Registers the tool by including QUICK_ADD_TASK_TOOL in the list returned by ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        // Task tools
        CREATE_TASK_TOOL,
        QUICK_ADD_TASK_TOOL,
        GET_TASKS_TOOL,
        GET_TASK_TOOL,
        UPDATE_TASK_TOOL,
        DELETE_TASK_TOOL,
        COMPLETE_TASK_TOOL,
        REOPEN_TASK_TOOL,
        SEARCH_TASKS_TOOL,
        MOVE_TASK_TOOL,
        BULK_MOVE_TASKS_TOOL,
        // Project tools
        GET_PROJECTS_TOOL,
        GET_PROJECT_TOOL,
        CREATE_PROJECT_TOOL,
        UPDATE_PROJECT_TOOL,
        DELETE_PROJECT_TOOL,
        // Section tools
        GET_SECTIONS_TOOL,
        CREATE_SECTION_TOOL,
        UPDATE_SECTION_TOOL,
        DELETE_SECTION_TOOL,
        // Label tools
        CREATE_LABEL_TOOL,
        GET_LABEL_TOOL,
        GET_LABELS_TOOL,
        UPDATE_LABEL_TOOL,
        DELETE_LABEL_TOOL,
        // Comment tools
        CREATE_COMMENT_TOOL,
        GET_COMMENT_TOOL,
        GET_COMMENTS_TOOL,
        UPDATE_COMMENT_TOOL,
        DELETE_COMMENT_TOOL,
      ],
    }));
  • Type guard function used in the handler to validate input arguments for the todoist_quick_add_task tool.
    function isQuickAddArgs(args: unknown): args is {
      text: string;
      note?: string;
      reminder?: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "text" in args &&
        typeof (args as { text: string }).text === "string"
      );
    }
Behavior2/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 mentions 'natural language parsing' but doesn't cover critical aspects like required permissions, error handling, rate limits, or what happens on success/failure. For a creation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence that front-loads the core purpose without unnecessary words. Every part ('Create a task,' 'Todoist's Quick Add feature,' 'natural language parsing') contributes essential information, making it maximally concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (creation with natural language parsing), no annotations, and no output schema, the description is minimally adequate. It covers the what and how but lacks details on behavioral traits, error cases, or output format, which would be needed for full contextual understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, such as formatting examples for 'reminder' or constraints on 'text.' This meets the baseline for high schema coverage.

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 ('Create a task') using a specific method ('Todoist's Quick Add feature with natural language parsing'), which distinguishes it from the sibling 'todoist_create_task' that likely uses structured inputs. It specifies both the verb and resource with unique implementation details.

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 when to use this tool by mentioning 'natural language parsing,' suggesting it's for quick, informal task creation versus structured alternatives. However, it doesn't explicitly state when not to use it or name specific alternatives like 'todoist_create_task,' leaving some ambiguity.

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/vitalio-sh/todoist-mcp-server-ext'

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