Skip to main content
Glama

trello_get_board_cards

Retrieve all cards from a Trello board with options to filter by status, include attachments, and view member details for organized project management.

Instructions

Get all cards from a Trello board with optional filtering and detailed information like attachments and members.

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 cards from (you can get this from list_boards)
attachmentsNoInclude attachment information: "cover" for cover images, "true" for all attachmentsfalse
membersNoInclude member information for each cardtrue
filterNoFilter cards by statusopen

Implementation Reference

  • The handler function that executes the trello_get_board_cards tool logic.
    export async function handleTrelloGetBoardCards(args: unknown) {
      try {
        const { apiKey, token, boardId, attachments, members, filter } = validateGetBoardCards(args);
        const client = new TrelloClient({ apiKey, token });
        
        const response = await client.getBoardCards(boardId, {
          ...(attachments && { attachments }),
          ...(members && { members }),
          ...(filter && { filter })
        });
        const cards = response.data;
        
        const result = {
          summary: `Found ${cards.length} card(s) in board`,
          boardId,
          cards: cards.map(card => ({
            id: card.id,
            name: card.name,
            description: card.desc || 'No description',
            url: card.shortUrl,
            listId: card.idList,
            position: card.pos,
            due: card.due,
            dueComplete: card.dueComplete,
            closed: card.closed,
            lastActivity: card.dateLastActivity,
            labels: card.labels?.map(label => ({
              id: label.id,
              name: label.name,
              color: label.color
            })) || [],
            members: card.members?.map(member => ({
              id: member.id,
              fullName: member.fullName,
              username: member.username
            })) || [],
            attachments: card.attachments?.map((attachment: any) => ({
              id: attachment.id,
              name: attachment.name,
              url: attachment.url,
              mimeType: attachment.mimeType,
              date: attachment.date
            })) || []
          })),
          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 cards: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
    }
  • The tool definition, including the schema for trello_get_board_cards.
    export const trelloGetBoardCardsTool: Tool = {
      name: 'trello_get_board_cards',
      description: 'Get all cards from a Trello board with optional filtering and detailed information like attachments and members.',
      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 cards from (you can get this from list_boards)',
            pattern: '^[a-f0-9]{24}$'
          },
          attachments: {
            type: 'string',
            enum: ['cover', 'true', 'false'],
            description: 'Include attachment information: "cover" for cover images, "true" for all attachments',
            default: 'false'
          },
          members: {
            type: 'string',
            enum: ['true', 'false'],
            description: 'Include member information for each card',
            default: 'true'
          },
          filter: {
            type: 'string',
            enum: ['all', 'open', 'closed'],
            description: 'Filter cards by status',
            default: 'open'
          }
        },
        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 full burden for behavioral disclosure. It mentions 'optional filtering and detailed information' but doesn't specify authentication requirements (though parameters suggest it), rate limits, pagination behavior, error conditions, or what happens when no cards exist. For a read operation with 6 parameters, this leaves significant behavioral gaps.

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

Conciseness4/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 cards from a Trello board') followed by key capabilities. There's no wasted text, though it could be slightly more structured for clarity.

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

Completeness3/5

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

Given 6 parameters, no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose and hints at some parameters, but doesn't address authentication needs, response format, error handling, or detailed behavioral context that would be helpful for an agent invoking this tool.

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%, providing complete parameter documentation. The description adds marginal value by mentioning 'optional filtering' (hinting at the filter parameter) and 'detailed information like attachments and members' (referencing those parameters), but doesn't provide additional semantic context beyond what's already in the schema descriptions.

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 cards') and resource ('from a Trello board'), with additional context about optional filtering and detailed information. It distinguishes from siblings like 'get_card' (single card) and 'trello_get_list_cards' (cards from a list), though it doesn't explicitly name these alternatives.

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

Usage Guidelines3/5

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

The description implies usage for retrieving cards from a board with optional details, but doesn't explicitly state when to use this versus alternatives like 'trello_get_list_cards' or 'get_card'. It mentions filtering capabilities which suggests context for when to apply filters, but lacks explicit guidance on tool selection.

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