Skip to main content
Glama
m0xai

Trello MCP Server with Python

by m0xai

get_lists

Retrieve all lists from a Trello board to organize tasks, track progress, and manage workflows using the board ID.

Instructions

Retrieves all lists on a given board.

Args:
    board_id (str): The ID of the board whose lists to retrieve.

Returns:
    List[TrelloList]: A list of list objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYes

Implementation Reference

  • The MCP tool handler function for get_lists that retrieves lists for a board by calling the ListService.
    async def get_lists(ctx: Context, board_id: str) -> List[TrelloList]:
        """Retrieves all lists on a given board.
    
        Args:
            board_id (str): The ID of the board whose lists to retrieve.
    
        Returns:
            List[TrelloList]: A list of list objects.
        """
        try:
            logger.info(f"Getting lists for board: {board_id}")
            result = await service.get_lists(board_id)
            logger.info(f"Successfully retrieved {len(result)} lists for board: {board_id}")
            return result
        except Exception as e:
            error_msg = f"Failed to get lists: {str(e)}"
            logger.error(error_msg)
            await ctx.error(error_msg)
            raise
  • Registration of the get_lists tool in the MCP server.
    mcp.add_tool(list.get_lists)
  • The underlying service method that calls the Trello API to fetch lists for the given board.
    async def get_lists(self, board_id: str) -> List[TrelloList]:
        """Retrieves all lists on a given board.
    
        Args:
            board_id (str): The ID of the board whose lists to retrieve.
    
        Returns:
            List[TrelloList]: A list of list objects.
        """
        response = await self.client.GET(f"/boards/{board_id}/lists")
        return [TrelloList(**list_data) for list_data in response]
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'retrieves' lists, implying a read-only operation, but doesn't mention potential side effects, error conditions, authentication needs, rate limits, or response format details beyond the return type. This is insufficient for a tool with no annotation coverage.

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 front-loaded with the core purpose in the first sentence, followed by structured Arg and Return sections that are clear and efficient. Every sentence adds value without redundancy, making it easy to scan and understand quickly.

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 the tool's low complexity (one parameter, no output schema, no annotations), the description covers the basic purpose and parameter semantics adequately. However, it lacks details on behavioral aspects like error handling or response structure, which would be helpful for an agent to use it correctly in varied scenarios.

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 description adds meaningful context for the single parameter by explaining that board_id identifies 'the board whose lists to retrieve,' which clarifies its purpose beyond the schema's minimal title ('Board Id'). With 0% schema description coverage and only one parameter, this adequately compensates, though it could specify format or constraints.

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') and resource ('all lists on a given board'), distinguishing it from sibling tools like get_board (which retrieves board details) or get_list (which retrieves a single list). It precisely defines what the tool does without ambiguity.

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 it retrieves lists for a given board, but it doesn't explicitly state when to use this tool versus alternatives like get_board (for board metadata) or get_cards (for cards on the board). No exclusions or prerequisites are mentioned, leaving some context gaps.

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