Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_create_label

Create custom labels in Todoist to organize tasks by category, priority, or context using name, color, favorites, and ordering options.

Instructions

Create a new label.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the label.
colorNoLabel color name or code (e.g., 'berry_red', '#FF0000') (optional).
isFavoriteNoWhether the label should be a favorite (optional).
orderNoThe order of the label in the list (optional).

Implementation Reference

  • Handler implementation for todoist_create_label tool. Validates input with isCreateLabelArgs type guard, calls todoistClient.addLabel(args), formats response using formatLabel helper, and handles errors.
    if (name === "todoist_create_label") {
      if (!isCreateLabelArgs(args)) {
        return { content: [{ type: "text", text: "Invalid arguments for create_label" }], isError: true };
      }
      try {
        const label = await todoistClient.addLabel(args);
        return { 
          content: [{ type: "text", text: `Label created:\n${formatLabel(label)}` }], 
          isError: false 
        };
      } catch (error: any) {
        return { content: [{ type: "text", text: `Error creating label: ${error.message}` }], isError: true };
      }
    }
  • Tool schema definition for todoist_create_label, including input schema with required 'name' and optional color, isFavorite, order.
    const CREATE_LABEL_TOOL: Tool = {
      name: "todoist_create_label",
      description: "Create a new label.",
      inputSchema: {
        type: "object",
        properties: {
          name: { type: "string", description: "The name of the label." },
          color: { type: "string", description: "Label color name or code (e.g., 'berry_red', '#FF0000') (optional)." },
          isFavorite: { type: "boolean", description: "Whether the label should be a favorite (optional)." },
          order: { type: "number", description: "The order of the label in the list (optional)." }
        },
        required: ["name"]
      }
    };
  • src/index.ts:1083-1121 (registration)
    Registration of all tools including todoist_create_label via CREATE_LABEL_TOOL in the ListToolsRequestSchema handler's tools array.
    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 helper function isCreateLabelArgs used to validate input arguments for the todoist_create_label handler.
    function isCreateLabelArgs(args: unknown): args is {
      name: string;
      color?: string;
      isFavorite?: boolean;
      order?: number;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "name" in args &&
        typeof (args as { name: string }).name === "string"
      );
    }
  • Helper function formatLabel used to format the output of created/updated labels in responses.
    function formatLabel(label: any): string {
      return `- ${label.name} (ID: ${label.id})${label.color ? `\n  Color: ${label.color}` : ''}${label.isFavorite ? `\n  Favorite: Yes` : ''}${label.order ? `\n  Order: ${label.order}`: ''}`;
    }
Behavior2/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 of behavioral disclosure. It states 'Create a new label,' which implies a write operation, but doesn't disclose any behavioral traits such as authentication requirements, rate limits, error conditions, or what happens on success (e.g., returns a label ID). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 ('Create a new label.') that is front-loaded and wastes no words. Every part of the sentence directly contributes to understanding the tool's purpose, making it appropriately concise for a simple creation tool.

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

Completeness2/5

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

Given the complexity of a mutation tool (creating a label) with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a label object or ID), any side effects, or error handling. For a tool that modifies data, this lack of context makes it inadequate for safe and effective use by an AI agent.

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?

The description adds no parameter information beyond what's already in the schema, which has 100% coverage with clear descriptions for all four parameters (name, color, isFavorite, order). Since schema_description_coverage is high, the baseline score is 3, as the schema adequately documents parameters without needing additional details in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create') and resource ('a new label'), making the purpose immediately understandable. It distinguishes from siblings like todoist_update_label or todoist_delete_label by specifying creation rather than modification or deletion. However, it doesn't explicitly differentiate from other creation tools like todoist_create_project or todoist_create_task, which would require mentioning it's specifically for labels.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a Todoist account), when to choose this over updating an existing label, or how it relates to sibling tools like todoist_get_labels for listing labels. Without such context, the agent must infer usage from the tool name alone.

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