Skip to main content
Glama

create-labels

Add color-coded labels to Trello boards to organize and categorize cards for better project management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelsYes

Implementation Reference

  • The handler function for the "create_label" tool, which extracts arguments and delegates to the LabelService.createLabel method to create a new label on a board.
    /**
     * Create a new label on a board
     * @param args - Tool arguments
     * @returns Promise resolving to the created label
     */
    create_label: async (args: any) => {
        const labelService = ServiceFactory.getInstance().getLabelService();
        return labelService.createLabel(args.boardId, args.name, args.color);
    },
  • The schema definition for the "create_label" tool, specifying the input parameters: boardId, name, and color.
        name: "create_label",
        description: "Create a new label on a board. Use this tool when you need to add a new label to a board for categorizing cards.",
        inputSchema: {
            type: "object",
            properties: {
                boardId: {
                    type: "string",
                    description: "ID of the board"
                },
                name: {
                    type: "string",
                    description: "Name of the label"
                },
                color: {
                    type: ["string", "null"],
                    enum: ["green", "yellow", "orange", "red", "purple", "blue", "sky", "lime", "pink", "black", null],
                    description: "Color of the label, or null for no color"
                }
            },
            required: ["boardId", "name", "color"]
        }
    },
  • The core implementation in LabelService.createLabel that makes the POST request to Trello's /labels endpoint to create the label.
    /**
     * Create a new label on a board
     * @param boardId - ID of the board
     * @param name - Name of the label
     * @param color - Color of the label
     * @returns Promise resolving to the created label
     */
    async createLabel(
        boardId: string,
        name: string,
        color: 'green' | 'yellow' | 'orange' | 'red' | 'purple' | 'blue' | 'sky' | 'lime' | 'pink' | 'black' | null
    ): Promise<TrelloLabel> {
        return this.trelloService.post<TrelloLabel>('/labels', {
            idBoard: boardId,
            name,
            color
        });
    }
  • src/index.ts:97-101 (registration)
    Registration of the list tools handler in the MCP server, which includes the "create_label" schema from trelloTools (aggregated from labelTools).
    server.setRequestHandler(ListToolsRequestSchema, async () => {
        return {
            tools: trelloTools
        };
    });
  • src/index.ts:127-140 (registration)
    The generic tool call handler registration that dispatches to the specific "create_label" handler from trelloToolHandlers (aggregated from labelToolHandlers).
    const toolName = request.params.name;
    // Use type assertion to tell TypeScript that toolName is a valid key
    const handler = trelloToolHandlers[toolName as keyof typeof trelloToolHandlers];
    
    if (!handler) {
        throw new McpError(
            ErrorCode.MethodNotFound,
            `Unknown tool: ${toolName}`
        );
    }
    
    // Execute the tool handler with the provided arguments
    const result = await handler(request.params.arguments);
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/v4lheru/trello-mcp-server'

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