Skip to main content
Glama
m0xai

Trello MCP Server with Python

by m0xai

get_boards

Retrieve all Trello boards for the authenticated user to manage and organize projects.

Instructions

Retrieves all boards for the authenticated user.

Returns:
    List[TrelloBoard]: A list of board objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function for 'get_boards' that retrieves all Trello boards for the user via the BoardService, logs the operation, and handles errors by notifying the context.
    async def get_boards(ctx: Context) -> List[TrelloBoard]:
        """Retrieves all boards for the authenticated user.
    
        Returns:
            List[TrelloBoard]: A list of board objects.
        """
        try:
            logger.info("Getting all boards")
            result = await service.get_boards()
            logger.info(f"Successfully retrieved {len(result)} boards")
            return result
        except Exception as e:
            error_msg = f"Failed to get boards: {str(e)}"
            logger.error(error_msg)
            await ctx.error(error_msg)
            raise
  • Registration of the 'get_boards' tool using mcp.add_tool(board.get_boards) within the register_tools function.
    mcp.add_tool(board.get_boards)
  • The BoardService.get_boards method, which performs the actual API call to fetch boards from Trello and parses them into TrelloBoard models. Called by the tool handler.
    async def get_boards(self, member_id: str = "me") -> List[TrelloBoard]:
        """Retrieves all boards for a given member.
    
        Args:
            member_id (str): The ID of the member whose boards to retrieve. Defaults to "me" for the authenticated user.
    
        Returns:
            List[TrelloBoard]: A list of board objects.
        """
        response = await self.client.GET(f"/members/{member_id}/boards")
        return [TrelloBoard(**board) for board in response]
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses that it retrieves data (implied read-only) and specifies it's for the authenticated user, but lacks details on rate limits, pagination, error handling, or what 'all boards' entails (e.g., archived boards). It adds some context but misses key behavioral traits.

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 sized with two sentences: one stating the purpose and one describing the return value. It is front-loaded with the core functionality, though the return description could be integrated more seamlessly. Minimal waste, but slight room for polish.

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 no annotations and no output schema, the description provides basic purpose and return type but lacks details on output structure (e.g., board object fields), authentication requirements, or error cases. For a retrieval tool with zero structured metadata, it is adequate but has clear gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description correctly omits parameter details, maintaining focus on the tool's purpose and output. Baseline is 4 for zero parameters, as it avoids unnecessary information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Retrieves'), resource ('all boards'), and scope ('for the authenticated user'), which distinguishes it from sibling tools like get_board (singular) and other non-board retrieval tools. It provides a complete purpose statement without being tautological.

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 by specifying 'for the authenticated user,' which suggests authentication context, but does not explicitly state when to use this tool versus alternatives like get_board (singular) or get_cards. No explicit exclusions or comparisons to siblings are provided.

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/m0xai/trello-mcp-server'

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