Skip to main content
Glama

trello_get_user_boards

Retrieve all Trello boards accessible to your account to explore and manage your workspace. Filter results by open, closed, or all boards as needed.

Instructions

Get all boards accessible to the current user. This is the starting point for exploring your Trello workspace.

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 'handleTrelloGetUserBoards' performs the logic of fetching user boards using the Trello API client.
    export async function handleTrelloGetUserBoards(args: unknown) {
      try {
        const { apiKey, token, filter } = validateGetUserBoards(args);
        const client = new TrelloClient({ apiKey, token });
        
        const response = await client.getCurrentUser();
        const user = response.data;
        
        const result = {
          summary: `User: ${user.fullName || user.username}`,
          user: {
            id: user.id,
            fullName: user.fullName,
            username: user.username,
            bio: user.bio,
            url: user.url,
            memberType: user.memberType,
            confirmed: user.confirmed
          },
          boards: user.boards?.filter((board: any) => {
            if (filter === 'all') return true;
            if (filter === 'closed') return board.closed;
            return !board.closed; // 'open' or default
          }).map((board: any) => ({
            id: board.id,
            name: board.name,
            description: board.desc || 'No description',
            url: board.shortUrl,
            closed: board.closed,
            lastActivity: board.dateLastActivity,
            permissions: board.prefs?.permissionLevel || 'unknown'
          })) || [],
          organizations: user.organizations?.map((org: any) => ({
            id: org.id,
            name: org.name,
            displayName: org.displayName,
            description: org.desc
          })) || [],
          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 user boards: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
    }
  • Input validation for 'trello_get_user_boards' tool using Zod.
    const validateGetUserBoards = (args: unknown) => {
      const schema = 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()
      });
      
      return schema.parse(args);
    };
  • MCP Tool registration definition for 'trello_get_user_boards'.
    export const trelloGetUserBoardsTool: Tool = {
      name: 'trello_get_user_boards',
      description: 'Get all boards accessible to the current user. This is the starting point for exploring your Trello workspace.',
      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']
      }
    };
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 retrieving 'all boards accessible to the current user' but doesn't specify whether this includes pagination, rate limits, authentication requirements beyond the parameters, or what the response format looks like. For a read operation with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 extremely concise with just two sentences, both of which add value. The first sentence states the core purpose, and the second provides helpful contextual framing. There's no wasted verbiage or redundancy.

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 operation with 3 parameters and no output schema, the description provides basic purpose and context but lacks details about response format, pagination, error handling, or authentication behavior. The 100% schema coverage helps with parameters, but overall completeness is only adequate given the tool's moderate complexity.

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?

The description doesn't mention any parameters, but the input schema has 100% description coverage, thoroughly documenting all three parameters including the 'filter' enum with clear options. The baseline score of 3 is appropriate since the schema does the heavy lifting, though the description adds no additional parameter context.

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 boards') and resource ('accessible to the current user'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from the sibling 'list_boards' tool, which appears to serve a similar function, so it doesn't reach the highest score.

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 context ('starting point for exploring your Trello workspace'), suggesting this is a foundational tool for initial discovery. However, it lacks explicit guidance on when to use this versus alternatives like 'list_boards' or 'trello_search', and doesn't mention any prerequisites or exclusions.

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