Skip to main content
Glama

edit_label

Modify label titles and color schemes on project boards to improve visual organization and categorization.

Instructions

Edit a label's title and colors

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID
label_idYesLabel ID
titleYesLabel title/text
bg_colorNoBackground color (hex)
colorNoText color (hex)

Implementation Reference

  • Handler function for 'edit_label' tool: destructures args, conditionally adds bg_color and color to labelData, performs PUT API request to update label, returns formatted response.
    async (args) => {
      const { board_id, label_id, title, bg_color, color } = args;
    
      const labelData: any = {
        label: title,
      };
    
      if (bg_color) {
        labelData.bg_color = bg_color;
      }
    
      if (color) {
        labelData.color = color;
      }
    
      const response = await api.put(
        `/projects/${board_id}/labels/${label_id}`,
        labelData
      );
      return formatResponse(response.data);
    }
  • Registers the 'edit_label' MCP tool with server.tool(), providing description, inline Zod input schema, and handler function.
    server.tool(
      "edit_label",
      "Edit a label's title and colors",
      {
        board_id: z.number().int().positive().describe("Board ID"),
        label_id: z.number().int().positive().describe("Label ID"),
        title: z.string().min(1).describe("Label title/text"),
        bg_color: z.string().optional().describe("Background color (hex)"),
        color: z.string().optional().describe("Text color (hex)"),
      },
      async (args) => {
        const { board_id, label_id, title, bg_color, color } = args;
    
        const labelData: any = {
          label: title,
        };
    
        if (bg_color) {
          labelData.bg_color = bg_color;
        }
    
        if (color) {
          labelData.color = color;
        }
    
        const response = await api.put(
          `/projects/${board_id}/labels/${label_id}`,
          labelData
        );
        return formatResponse(response.data);
      }
    );
  • Zod schema definition for EditLabel inputs, matching the inline schema used in the tool registration.
    export const EditLabelSchema = z.object({
      board_id: z.number().int().positive(),
      label_id: z.number().int().positive(),
      title: z.string().min(1),
      bg_color: z.string().optional(),
      color: z.string().optional(),
    });
  • src/index.ts:25-25 (registration)
    Top-level registration call that invokes registerLabelTools to add all label tools, including 'edit_label', to the MCP server.
    registerLabelTools(server);
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 states 'Edit' which implies a mutation operation, but doesn't mention permissions required, whether changes are reversible, potential side effects, or what the response looks like. This is inadequate for a mutation tool with zero annotation coverage.

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 directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens when editing a label (e.g., whether it affects existing tasks), error conditions, or return values. The agent would need to guess about behavioral aspects beyond the basic edit action.

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 adds minimal value by mentioning 'title and colors' which aligns with the 'title', 'bg_color', and 'color' parameters, but doesn't provide additional context beyond what the schema already specifies. 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.

Purpose4/5

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

The description clearly states the action ('Edit') and the resource ('a label's title and colors'), making the purpose immediately understandable. It specifies what aspects of a label can be modified, though it doesn't explicitly differentiate from sibling tools like 'update_task' or 'create_label' 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 like 'create_label', 'delete_label', or 'remove_label'. It lacks context about prerequisites (e.g., needing an existing label) or typical use cases, leaving the agent to infer usage from the tool name and parameters 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/danieliser/fluent-boards-mcp-server'

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