Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_update_label

Modify an existing Todoist label by updating its name, color, favorite status, or order using the label ID.

Instructions

Update an existing label by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelIdYesThe ID of the label to update.
nameNoNew name for the label (optional).
colorNoNew color for the label (optional).
isFavoriteNoNew favorite status (optional).
orderNoNew order for the label (optional).

Implementation Reference

  • Executes the todoist_update_label tool: validates args with isUpdateLabelArgs, calls todoistClient.updateLabel(labelId, updateArgs), formats response with formatLabel.
    if (name === "todoist_update_label") {
      if (!isUpdateLabelArgs(args)) {
        return { content: [{ type: "text", text: "Invalid arguments for update_label" }], isError: true };
      }
      try {
        const { labelId, ...updateArgs } = args;
        const updatedLabel = await todoistClient.updateLabel(labelId, updateArgs);
        return { 
          content: [{ type: "text", text: `Label updated:\n${formatLabel(updatedLabel)}` }], 
          isError: false 
        };
      } catch (error: any) {
        return { content: [{ type: "text", text: `Error updating label: ${error.message}` }], isError: true };
      }
    }
  • Input schema and metadata definition for the todoist_update_label tool.
    const UPDATE_LABEL_TOOL: Tool = {
      name: "todoist_update_label",
      description: "Update an existing label by its ID.",
      inputSchema: {
        type: "object",
        properties: {
          labelId: { type: "string", description: "The ID of the label to update." },
          name: { type: "string", description: "New name for the label (optional)." },
          color: { type: "string", description: "New color for the label (optional)." },
          isFavorite: { type: "boolean", description: "New favorite status (optional)." },
          order: { type: "number", description: "New order for the label (optional)." }
        },
        required: ["labelId"]
      }
    };
  • src/index.ts:1109-1114 (registration)
    Registers UPDATE_LABEL_TOOL in the array of tools advertised via ListToolsRequestSchema handler.
    CREATE_LABEL_TOOL,
    GET_LABEL_TOOL,
    GET_LABELS_TOOL,
    UPDATE_LABEL_TOOL,
    DELETE_LABEL_TOOL,
    // Comment tools
  • Type guard function to validate input arguments for the todoist_update_label tool.
    function isUpdateLabelArgs(args: unknown): args is {
      labelId: string;
      name?: string;
      color?: string;
      isFavorite?: boolean;
      order?: number;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "labelId" in args &&
        typeof (args as { labelId: string }).labelId === "string"
      );
    }
  • Helper function used to format the updated label details in the tool response.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation but doesn't mention permission requirements, whether changes are reversible, error conditions, or what happens to unspecified fields. For a mutation tool, this leaves significant behavioral gaps.

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, clear sentence that gets straight to the point with no unnecessary words. It's appropriately sized for a straightforward update operation and front-loads the essential information.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns, error handling, or behavioral constraints. Given the complexity of updating a resource and the lack of structured metadata, more context is needed for effective 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%, so all parameters are documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema, but the baseline score of 3 is appropriate since the schema adequately covers parameter documentation.

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 ('Update') and resource ('an existing label by its ID'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'todoist_update_task' or 'todoist_update_project' beyond the resource type, missing explicit sibling distinction.

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 like 'todoist_create_label' for new labels or other update tools. It mentions the required 'labelId' parameter but offers no context about prerequisites or typical use cases.

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