Skip to main content
Glama
m0xai

Trello MCP Server with Python

by m0xai

create_list

Add a new list to a Trello board to organize tasks and workflows. Specify board ID, list name, and position for structured project management.

Instructions

Creates a new list on a given board.

Args:
    board_id (str): The ID of the board to create the list in.
    name (str): The name of the new list.
    pos (str, optional): The position of the new list. Can be "top" or "bottom". Defaults to "bottom".

Returns:
    TrelloList: The newly created list object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYes
nameYes
posNobottom

Implementation Reference

  • MCP tool handler for create_list: executes the logic, handles errors, logs, and calls the service.
    async def create_list(
        ctx: Context, board_id: str, name: str, pos: str = "bottom"
    ) -> TrelloList:
        """Creates a new list on a given board.
    
        Args:
            board_id (str): The ID of the board to create the list in.
            name (str): The name of the new list.
            pos (str, optional): The position of the new list. Can be "top" or "bottom". Defaults to "bottom".
    
        Returns:
            TrelloList: The newly created list object.
        """
        try:
            logger.info(f"Creating list '{name}' in board: {board_id}")
            result = await service.create_list(board_id, name, pos)
            logger.info(f"Successfully created list '{name}' in board: {board_id}")
            return result
        except Exception as e:
            error_msg = f"Failed to create list: {str(e)}"
            logger.error(error_msg)
            await ctx.error(error_msg)
            raise
  • Registers the create_list tool handler with the MCP server.
    mcp.add_tool(list.create_list)
  • Core service method that performs the actual Trello API call to create a list.
    async def create_list(
        self, board_id: str, name: str, pos: str = "bottom"
    ) -> TrelloList:
        """Creates a new list on a given board.
    
        Args:
            board_id (str): The ID of the board to create the list in.
            name (str): The name of the new list.
            pos (str, optional): The position of the new list. Can be "top" or "bottom". Defaults to "bottom".
    
        Returns:
            TrelloList: The newly created list object.
        """
        data = {"name": name, "idBoard": board_id, "pos": pos}
        response = await self.client.POST("/lists", data=data)
        return TrelloList(**response)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation but doesn't mention required permissions, whether it's idempotent, rate limits, error conditions, or what happens if a list with the same name exists. The return type 'TrelloList' is mentioned but not explained. This leaves significant behavioral gaps for a mutation tool.

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 perfectly structured and concise. The first sentence states the core purpose, followed by clearly labeled sections for Args and Returns. Every sentence earns its place by providing essential information without redundancy. The formatting with parameter explanations is highly readable and front-loaded.

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 3-parameter mutation tool with no annotations and no output schema, the description does an adequate job but has clear gaps. The parameter explanations are excellent, but behavioral aspects like permissions, error handling, and the structure of the returned 'TrelloList' object are missing. The description provides minimum viable information but doesn't fully address the complexity of a creation operation in a collaborative tool like Trello.

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 provides excellent parameter semantics despite 0% schema description coverage. It clearly explains all three parameters: board_id ('The ID of the board to create the list in'), name ('The name of the new list'), and pos ('The position of the new list. Can be "top" or "bottom". Defaults to "bottom"'). This fully compensates for the lack of schema descriptions, adding meaningful context beyond basic type information.

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 verb 'creates' and the resource 'new list on a given board', making the purpose explicit. It distinguishes from siblings like 'create_card' or 'create_board_label' by specifying it creates a list rather than other Trello entities. However, it doesn't explicitly differentiate from 'create_checklist' which is a similar sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing board access), when not to use it, or how it relates to sibling tools like 'create_card' or 'create_checklist'. The agent must infer usage from the tool name alone.

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