Skip to main content
Glama

create-label

Add a colored label to a Trello board to organize and categorize cards for better visual management and workflow tracking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesID of the board to create the label in
nameYesName of the label
colorYesColor of the label

Implementation Reference

  • The handler function that executes the create-label tool logic by sending a POST request to the Trello API to create a new label on the specified board.
    async ({ boardId, name, color }) => {
    	try {
    		const response = await fetch(
    			`https://api.trello.com/1/labels?key=${trelloApiKey}&token=${trelloApiToken}`,
    			{
    				method: 'POST',
    				headers: {
    					'Content-Type': 'application/json',
    				},
    				body: JSON.stringify({
    					name,
    					color,
    					idBoard: boardId,
    				}),
    			}
    		);
    		const data = await response.json();
    		return {
    			content: [
    				{
    					type: 'text',
    					text: JSON.stringify(data),
    				},
    			],
    		};
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: 'text',
    					text: `Error creating label: ${error}`,
    				},
    			],
    			isError: true,
    		};
    	}
    }
  • Zod schema defining the input parameters for the create-label tool: boardId, name, and color.
    	boardId: z.string().describe('ID of the board to create the label in'),
    	name: z.string().describe('Name of the label'),
    	color: z
    		.enum(['yellow', 'purple', 'blue', 'red', 'green', 'orange', 'black', 'sky', 'pink', 'lime'])
    		.describe('Color of the label'),
    },
  • src/index.ts:330-375 (registration)
    Registration of the create-label tool using server.tool, including schema and inline handler.
    	'create-label',
    	{
    		boardId: z.string().describe('ID of the board to create the label in'),
    		name: z.string().describe('Name of the label'),
    		color: z
    			.enum(['yellow', 'purple', 'blue', 'red', 'green', 'orange', 'black', 'sky', 'pink', 'lime'])
    			.describe('Color of the label'),
    	},
    	async ({ boardId, name, color }) => {
    		try {
    			const response = await fetch(
    				`https://api.trello.com/1/labels?key=${trelloApiKey}&token=${trelloApiToken}`,
    				{
    					method: 'POST',
    					headers: {
    						'Content-Type': 'application/json',
    					},
    					body: JSON.stringify({
    						name,
    						color,
    						idBoard: boardId,
    					}),
    				}
    			);
    			const data = await response.json();
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(data),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error creating label: ${error}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	}
    );
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/praveencs87/trello-mcp'

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