Skip to main content
Glama

list_boards

Retrieve all Trello boards accessible to your account, with options to filter by open, closed, or all boards for quick access and organization.

Instructions

List all Trello boards accessible to the user. Use this to see all boards you have access to, or filter by status.

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)
filterNoFilter boards by status: "open" for active boards, "closed" for archived boards, "all" for bothopen

Implementation Reference

  • The handler function that executes the logic for the list_boards tool. It calls the Trello client to retrieve boards and formats the output.
    export async function handleListBoards(args: unknown) {
      try {
        const { apiKey, token, filter } = validateListBoards(args);
        const client = new TrelloClient({ apiKey, token });
        
        const response = await client.getMyBoards(filter);
        const boards = response.data;
        
        const summary = `Found ${boards.length} ${filter} board(s)`;
        const boardList = boards.map(board => ({
          id: board.id,
          name: board.name,
          description: board.desc || 'No description',
          url: board.shortUrl,
          lastActivity: board.dateLastActivity,
          closed: board.closed
        }));
        
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify({
                summary,
                boards: boardList,
                rateLimit: response.rateLimit
              }, 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 listing boards: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
    }
  • The tool definition for list_boards, including its name and input schema.
    export const listBoardsTool: Tool = {
      name: 'list_boards',
      description: 'List all Trello boards accessible to the user. Use this to see all boards you have access to, or filter by status.',
      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)'
          },
          filter: {
            type: 'string',
            enum: ['all', 'open', 'closed'],
            description: 'Filter boards by status: "open" for active boards, "closed" for archived boards, "all" for both',
            default: 'open'
          }
        },
        required: ['apiKey', 'token']
      }
    };
  • The validation schema for the input arguments of list_boards.
    export const listBoardsSchema = z.object({
      apiKey: z.string().min(1, 'API key is required'),
      token: z.string().min(1, 'Token is required'),
      filter: z.enum(['all', 'open', 'closed']).optional().default('open')
    });
    
    export const getBoardSchema = z.object({
      apiKey: z.string().min(1, 'API key is required'),
      token: z.string().min(1, 'Token is required'),
      boardId: trelloIdSchema,
      includeDetails: z.boolean().optional().default(false)
    });
    
    export const getBoardListsSchema = z.object({
      apiKey: z.string().min(1, 'API key is required'),
      token: z.string().min(1, 'Token is required'),
      boardId: trelloIdSchema,
      filter: z.enum(['all', 'open', 'closed']).optional().default('open')
    });
    
    export const createCardSchema = z.object({
      apiKey: z.string().min(1, 'API key is required'),
      token: z.string().min(1, 'Token is required'),
      name: z.string().min(1, 'Card name is required').max(16384, 'Card name too long'),
      desc: z.string().max(16384, 'Description too long').optional(),
      idList: trelloIdSchema,
      pos: z.union([z.number().min(0), z.enum(['top', 'bottom'])]).optional(),
      due: z.string().datetime().optional(),
      idMembers: z.array(trelloIdSchema).optional(),
      idLabels: z.array(trelloIdSchema).optional()
    });
    
    export const updateCardSchema = z.object({
      apiKey: z.string().min(1, 'API key is required'),
      token: z.string().min(1, 'Token is required'),
      cardId: trelloIdSchema,
      name: z.string().min(1).max(16384).optional(),
      desc: z.string().max(16384).optional(),
      closed: z.boolean().optional(),
      due: z.string().datetime().nullable().optional(),
      dueComplete: z.boolean().optional(),
      idList: trelloIdOptionalSchema,
      pos: z.union([z.number().min(0), z.enum(['top', 'bottom'])]).optional(),
      idMembers: z.array(trelloIdSchema).optional(),
      idLabels: z.array(trelloIdSchema).optional()
    });
    
    export const moveCardSchema = z.object({
      apiKey: z.string().min(1, 'API key is required'),
      token: z.string().min(1, 'Token is required'),
      cardId: trelloIdSchema,
      idList: trelloIdSchema,
      pos: z.union([z.number().min(0), z.enum(['top', 'bottom'])]).optional()
    });
    
    export const getCardSchema = z.object({
      apiKey: z.string().min(1, 'API key is required'),
      token: z.string().min(1, 'Token is required'),
      cardId: trelloIdSchema,
      includeDetails: z.boolean().optional().default(false)
    });
    
    export const deleteCardSchema = z.object({
      apiKey: z.string().min(1, 'API key is required'),
      token: z.string().min(1, 'Token is required'),
      cardId: trelloIdSchema
    });
    
    export function validateCredentials(data: unknown) {
      return credentialsSchema.parse(data);
    }
    
    export function validateListBoards(data: unknown) {
      return listBoardsSchema.parse(data);
    }
    
    export function validateGetBoard(data: unknown) {
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. While it mentions the filtering capability, it doesn't describe important behavioral aspects like pagination behavior, rate limits, authentication requirements (beyond what's in the schema), error conditions, or what 'accessible to the user' means in practice (personal vs shared boards).

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 clear sentences that efficiently communicate the core functionality. The first sentence states the primary purpose, and the second adds important context about filtering. There's no wasted verbiage or unnecessary elaboration.

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?

For a read-only listing tool with no output schema, the description provides adequate but minimal context. It covers the basic purpose and filtering capability, but lacks details about return format, pagination, or how results are structured. Given the 3 parameters and absence of annotations/output schema, more behavioral context would be helpful.

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?

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description mentions filtering by status which aligns with the 'filter' parameter, but adds no additional semantic context beyond what the schema provides. The baseline score of 3 is appropriate when the schema does the heavy lifting.

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 ('List all Trello boards') and resource ('accessible to the user'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'trello_get_user_boards' or 'trello_search', which appear to offer similar board-related functionality.

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 usage context ('to see all boards you have access to, or filter by status'), but doesn't explicitly state when to use this tool versus alternatives like 'trello_get_user_boards' or 'trello_search'. The guidance is implied rather than explicit about 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