Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_get_labels

Retrieve all labels from Todoist with pagination support to manage and organize tasks efficiently.

Instructions

Get all labels. Supports pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor for next page (optional).
limitNoMaximum number of labels to return (default: 50) (optional).

Implementation Reference

  • Handler implementation for 'todoist_get_labels' tool. Validates args with isGetLabelsArgs, calls todoistClient.getLabels(params), formats results using formatLabel, handles pagination cursor, and returns formatted text response.
    if (name === "todoist_get_labels") {
      if (!isGetLabelsArgs(args)) {
        return { content: [{ type: "text", text: "Invalid arguments for get_labels. This tool takes an optional cursor and limit." }], isError: true };
      }
      try {
        const params: any = {};
        if (args.cursor) params.cursor = args.cursor;
        if (args.limit) params.limit = args.limit;
        
        const labelsResponse = await todoistClient.getLabels(params); 
        const labelList = labelsResponse.results?.map(formatLabel).join('\n\n') || 'No labels found';
        const nextCursor = labelsResponse.nextCursor ? `\n\nNext cursor for more labels: ${labelsResponse.nextCursor}` : '';
    
        return {
          content: [{
            type: "text",
            text: `Labels:\n${labelList}${nextCursor}`
          }],
          isError: false
        };
      } catch (error: any) {
        return { content: [{ type: "text", text: `Error getting labels: ${error.message}` }], isError: true };
      }
    }
  • Tool schema definition for 'todoist_get_labels', specifying input schema with optional cursor and limit for pagination.
    const GET_LABELS_TOOL: Tool = {
      name: "todoist_get_labels",
      description: "Get all labels. Supports pagination.",
      inputSchema: {
        type: "object",
        properties: {
          cursor: { 
            type: "string", 
            description: "Pagination cursor for next page (optional)." 
          },
          limit: { 
            type: "number", 
            description: "Maximum number of labels to return (default: 50) (optional)." 
          }
        }
      }
    };
  • src/index.ts:1083-1121 (registration)
    Registration of all tools including 'todoist_get_labels' (as GET_LABELS_TOOL) in the ListToolsRequestSchema handler, making it discoverable by MCP clients.
    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,
      ],
    }));
  • Helper function formatLabel used in the get_labels handler to format individual label details for output.
    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}`: ''}`;
    }
  • Type guard helper isGetLabelsArgs for validating optional cursor and limit arguments in the todoist_get_labels handler.
    function isGetLabelsArgs(args: unknown): args is { 
      cursor?: string;
      limit?: number;
    } { 
      return typeof args === "object" && args !== null;
    }
Behavior3/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 adds value by mentioning pagination support, which is not obvious from the input schema alone, but lacks details on permissions, rate limits, error handling, or what the output looks like (e.g., format of returned labels). For a read operation with no annotations, this is a minimal but not comprehensive disclosure.

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 extremely concise with two sentences that directly convey the core functionality and a key behavioral trait (pagination). It is front-loaded with the main purpose and wastes no words, making it efficient and easy to parse.

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 low complexity (a read operation with two optional parameters) and 100% schema coverage, the description is somewhat complete but has gaps. It lacks output schema, so it doesn't explain return values (e.g., label structure), and with no annotations, it misses behavioral details like safety or constraints. The description covers basics but could be more informative for agent use.

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 schema description coverage is 100%, with both parameters ('cursor' and 'limit') well-documented in the schema. The description adds no additional parameter semantics beyond implying pagination through the phrase 'Supports pagination,' which loosely relates to the 'cursor' parameter but doesn't explain its usage or format. Baseline 3 is appropriate since the schema does the heavy lifting.

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 verb ('Get') and resource ('all labels'), making the purpose immediately understandable. It distinguishes from sibling tools like 'todoist_get_label' (singular) by specifying 'all labels', though it doesn't explicitly contrast with other list tools like 'todoist_get_projects' or 'todoist_get_tasks' beyond the resource name.

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 mentions pagination but doesn't specify scenarios where fetching all labels is appropriate over other operations or how it relates to sibling tools like 'todoist_get_label' for individual label retrieval. There are no explicit when/when-not instructions or named alternatives.

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