Skip to main content
Glama

add-label

Add a label to a Trello card using its ID to organize and categorize tasks within project management workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardIdYesID of the card to add the label to
labelIdYesID of the label to add

Implementation Reference

  • The handler function that adds a label to a specified card by sending a POST request to the Trello API endpoint /cards/{cardId}/idLabels with the labelId as the value.
    async ({ cardId, labelId }) => {
    	try {
    		const response = await fetch(
    			`https://api.trello.com/1/cards/${cardId}/idLabels?key=${credentials.apiKey}&token=${credentials.apiToken}`,
    			{
    				method: 'POST',
    				headers: {
    					'Content-Type': 'application/json',
    				},
    				body: JSON.stringify({
    					value: labelId,
    				}),
    			}
    		);
    		const data = await response.json();
    		return {
    			content: [
    				{
    					type: 'text',
    					text: JSON.stringify(data),
    				},
    			],
    		};
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: 'text',
    					text: `Error adding label to card: ${error}`,
    				},
    			],
    			isError: true,
    		};
    	}
    }
  • Zod schema defining the input parameters: cardId and labelId for the add-label tool.
    {
    	cardId: z.string().describe('ID of the card to add the label to'),
    	labelId: z.string().describe('ID of the label to add'),
    },
  • Local registration of the 'add-label' tool using McpServer's tool method, including schema and handler.
    server.tool(
    	'add-label',
    	{
    		cardId: z.string().describe('ID of the card to add the label to'),
    		labelId: z.string().describe('ID of the label to add'),
    	},
    	async ({ cardId, labelId }) => {
    		try {
    			const response = await fetch(
    				`https://api.trello.com/1/cards/${cardId}/idLabels?key=${credentials.apiKey}&token=${credentials.apiToken}`,
    				{
    					method: 'POST',
    					headers: {
    						'Content-Type': 'application/json',
    					},
    					body: JSON.stringify({
    						value: labelId,
    					}),
    				}
    			);
    			const data = await response.json();
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(data),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error adding label to card: ${error}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	}
    );
  • src/index.ts:91-91 (registration)
    Top-level call to registerLabelsTools function, which includes the registration of the 'add-label' tool.
    registerLabelsTools(server, credentials);
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/adriangrahldev/advanced-trello-mcp-server'

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