Skip to main content
Glama

get_board_details

Retrieve comprehensive details about a Trello board, including its lists and cards, to analyze board structure and content for project management.

Instructions

Get detailed information about a specific Trello board, including its lists and cards. Useful for understanding board structure and content.

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)
boardIdYesThe ID of the board to retrieve (you can get this from list_boards)
includeDetailsNoInclude lists and cards in the response for complete board overview

Implementation Reference

  • The handler function that executes the logic for 'get_board_details' tool.
    export async function handleGetBoardDetails(args: unknown) {
      try {
        const { apiKey, token, boardId, includeDetails } = validateGetBoard(args);
        const client = new TrelloClient({ apiKey, token });
        
        const response = await client.getBoard(boardId, includeDetails);
        const board = response.data;
        
        const result = {
          summary: `Board: ${board.name}`,
          board: {
            id: board.id,
            name: board.name,
            description: board.desc || 'No description',
            url: board.shortUrl,
            lastActivity: board.dateLastActivity,
            closed: board.closed,
            permissions: board.prefs?.permissionLevel || 'unknown',
            ...(includeDetails && {
              lists: board.lists?.map(list => ({
                id: list.id,
                name: list.name,
                position: list.pos,
                closed: list.closed
              })) || [],
              cards: board.cards?.map(card => ({
                id: card.id,
                name: card.name,
                description: card.desc,
                url: card.shortUrl,
                listId: card.idList,
                position: card.pos,
                due: card.due,
                closed: card.closed,
                labels: card.labels?.map(label => ({
                  id: label.id,
                  name: label.name,
                  color: label.color
                })) || []
              })) || []
            })
          },
          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 details: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
    }
  • The MCP Tool definition for 'get_board_details'.
    export const getBoardDetailsTool: Tool = {
      name: 'get_board_details',
      description: 'Get detailed information about a specific Trello board, including its lists and cards. Useful for understanding board structure and content.',
      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: 'The ID of the board to retrieve (you can get this from list_boards)',
            pattern: '^[a-f0-9]{24}$'
          },
          includeDetails: {
            type: 'boolean',
            description: 'Include lists and cards in the response for complete board overview',
            default: false
          }
        },
        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 mentions what information is retrieved ('detailed information... including lists and cards') but doesn't disclose important behavioral aspects: authentication requirements (though the schema covers this), rate limits, whether this is a read-only operation, what happens when boardId is invalid, or response format details. For a tool with no annotation coverage, 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 appropriately concise with two sentences. The first sentence states the core purpose, and the second provides usage context. Both sentences earn their place, though the second could be more specific. The structure is front-loaded with the main functionality stated first.

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 4 parameters with 100% schema coverage but no annotations and no output schema, the description provides adequate but incomplete context. It covers the tool's purpose and general use case but lacks details about authentication behavior, error conditions, rate limits, and response format. For a tool that retrieves potentially complex board data, more context about what 'detailed information' includes would be helpful, especially without an output schema.

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 already fully documents all parameters. The description adds minimal value beyond the schema - it mentions 'including its lists and cards' which relates to the 'includeDetails' parameter, but doesn't provide additional semantic context about when to use includeDetails=true versus false. This meets the baseline expectation when schema coverage is complete.

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 tool's purpose: 'Get detailed information about a specific Trello board, including its lists and cards.' It specifies the verb ('Get'), resource ('Trello board'), and scope ('lists and cards'). However, it doesn't explicitly differentiate from sibling tools like 'trello_get_board_cards' or 'trello_get_board_labels', which reduces clarity about when to use this comprehensive tool versus more specific ones.

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 provides some implied usage guidance with 'Useful for understanding board structure and content,' suggesting this is for comprehensive overviews. However, it doesn't explicitly state when to use this tool versus alternatives like 'trello_get_board_cards' (which might be better for just cards) or 'list_boards' (which lists multiple boards). No explicit when-not-to-use guidance or prerequisites are mentioned.

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