Skip to main content
Glama

trello_get_board_labels

Retrieve all available labels from a specific Trello board to categorize and organize cards effectively.

Instructions

Get all labels available on a specific Trello board for categorizing cards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesTrello API key (automatically provided by Claude.app from your stored credentials)
tokenYesTrello API token (automatically provided by Claude.app from your stored credentials)
boardIdYesID of the board to get labels for

Implementation Reference

  • The handler function that executes the trello_get_board_labels tool.
    export async function handleTrelloGetBoardLabels(args: unknown) {
      try {
        const { apiKey, token, boardId } = validateGetBoardLabels(args);
        const client = new TrelloClient({ apiKey, token });
        
        const response = await client.getBoardLabels(boardId);
        const labels = response.data;
        
        const result = {
          summary: `Found ${labels.length} label(s) on board`,
          boardId,
          labels: labels.map(label => ({
            id: label.id,
            name: label.name,
            color: label.color,
            uses: label.uses
          })),
          rateLimit: response.rateLimit
        };
        
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof z.ZodError 
          ? formatValidationError(error)
          : error instanceof Error 
            ? error.message 
            : 'Unknown error occurred';
            
        return {
          content: [
            {
              type: 'text' as const,
              text: `Error getting board labels: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
    }
  • Input validation schema for the tool arguments.
    const validateGetBoardLabels = (args: unknown) => {
      const schema = z.object({
        apiKey: z.string().min(1, 'API key is required'),
        token: z.string().min(1, 'Token is required'),
        boardId: z.string().regex(/^[a-f0-9]{24}$/, 'Invalid board ID format')
      });
      
      return schema.parse(args);
    };
  • Registration of the tool with its name, description, and input schema.
    export const trelloGetBoardLabelsTool: Tool = {
      name: 'trello_get_board_labels',
      description: 'Get all labels available on a specific Trello board for categorizing cards.',
      inputSchema: {
        type: 'object',
        properties: {
          apiKey: {
            type: 'string',
            description: 'Trello API key (automatically provided by Claude.app from your stored credentials)'
          },
          token: {
            type: 'string',
            description: 'Trello API token (automatically provided by Claude.app from your stored credentials)'
          },
          boardId: {
            type: 'string',
            description: 'ID of the board to get labels for',
            pattern: '^[a-f0-9]{24}$'
          }
        },
        required: ['apiKey', 'token', 'boardId']
      }
    };
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 it 'gets' labels, implying a read-only operation, but doesn't cover critical aspects like authentication needs (though parameters hint at API credentials), rate limits, error handling, or output format (e.g., whether it returns a list of label objects with names/colors). This leaves significant gaps for a tool with no output schema.

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 front-loads the core purpose ('Get all labels available on a specific Trello board') and adds value with the clarifying phrase 'for categorizing cards.' There is no wasted verbiage or redundancy, making it highly concise and well-structured.

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?

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is incomplete. It lacks behavioral details (e.g., authentication, output format), usage guidelines, and fails to compensate for the absence of annotations. While concise, it doesn't provide enough context for an agent to confidently invoke the tool without external knowledge.

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%, so the schema fully documents the three parameters (apiKey, token, boardId). The description adds no parameter-specific information beyond implying 'boardId' targets 'a specific Trello board.' This meets the baseline of 3, as the schema handles the heavy lifting, but the description doesn't enhance understanding of parameter usage or constraints.

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 ('Get all labels') and resource ('on a specific Trello board'), with the purpose of 'categorizing cards' adding useful context. It distinguishes from siblings like 'get_board_details' or 'get_card' by focusing specifically on labels, though it doesn't explicitly contrast with other label-related tools (none exist in the sibling list).

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?

No guidance is provided on when to use this tool versus alternatives. While the description implies it's for retrieving labels for categorization, it doesn't mention prerequisites (e.g., needing board access), exclusions, or comparisons to other tools like 'trello_search' that might also find labels. The agent must infer usage from the purpose 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/kocakli/Trello-Desktop-MCP'

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