Skip to main content
Glama

create_label

Add a new label to a project board by specifying its title, background color, and text color to organize and categorize tasks.

Instructions

Create a new label on a board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID
titleYesLabel title/text
bg_colorYesBackground color (hex) - e.g., #4bce97
colorNoText color (hex) - defaults to #1B2533#1B2533

Implementation Reference

  • The handler function for the 'create_label' tool. It destructures the arguments, prepares the label data, makes a POST request to the API to create the label, and formats the response.
    async (args) => {
      const { board_id, title, bg_color, color } = args;
    
      const labelData: any = {
        label: title,
        bg_color,
        color,
      };
    
      const response = await api.post(
        `/projects/${board_id}/labels`,
        labelData
      );
      return formatResponse(response.data);
    }
  • Registers the 'create_label' tool with the MCP server, providing name, description, input schema, and handler function.
    server.tool(
      "create_label",
      "Create a new label on a board",
      {
        board_id: z.number().int().positive().describe("Board ID"),
        title: z.string().min(1).describe("Label title/text"),
        bg_color: z.string().describe("Background color (hex) - e.g., #4bce97"),
        color: z
          .string()
          .default("#1B2533")
          .describe("Text color (hex) - defaults to #1B2533"),
      },
      async (args) => {
        const { board_id, title, bg_color, color } = args;
    
        const labelData: any = {
          label: title,
          bg_color,
          color,
        };
    
        const response = await api.post(
          `/projects/${board_id}/labels`,
          labelData
        );
        return formatResponse(response.data);
      }
    );
  • Zod schema definition for CreateLabel inputs, matching the inline schema used in the tool registration.
    export const CreateLabelSchema = z.object({
      board_id: z.number().int().positive(),
      title: z.string().min(1),
      bg_color: z.string(),
      color: z.string().default("#1B2533"),
    });
  • src/index.ts:25-25 (registration)
    Calls registerLabelTools to register all label-related tools, including 'create_label', on 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. 'Create a new label' implies a write operation, but it doesn't specify permissions required, whether the operation is idempotent, rate limits, or what happens on success/failure (e.g., returns 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 that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place.

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 incomplete. It doesn't explain behavioral aspects like permissions, side effects, or return values. Given the complexity of creating a resource and the lack of structured data, the description should provide more context to guide the agent effectively.

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%, with all parameters clearly documented in the schema (board_id, title, bg_color, color with default). The description adds no additional parameter semantics beyond what's in the schema, such as format examples for colors or constraints on title length. Baseline 3 is appropriate when 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 action ('Create') and resource ('new label on a board'), making the purpose immediately understandable. It distinguishes from siblings like 'add_label' (which might add existing labels) and 'edit_label' (which modifies existing ones) by specifying 'new'. However, it doesn't explicitly mention what distinguishes it from 'add_label' beyond the 'new' implication.

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 'add_label' or 'edit_label'. It doesn't mention prerequisites (e.g., needing board access) or exclusions (e.g., not for updating existing labels). The agent must infer usage from the name and context 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