Skip to main content
Glama
m0xai

Trello MCP Server with Python

by m0xai

create_checklist

Add a new checklist to a Trello card to organize tasks and track progress. Specify card ID, checklist name, and optional position.

Instructions

Create a new checklist on a card.

Args:
    card_id (str): The ID of the card to create the checklist on
    name (str): The name of the checklist
    pos (Optional[str]): The position of the checklist (top, bottom, or a positive number)

Returns:
    Dict: The created checklist data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_idYes
nameYes
posNo

Implementation Reference

  • MCP tool handler for create_checklist: thin wrapper that delegates to ChecklistService.
    async def create_checklist(card_id: str, name: str, pos: str | None = None) -> Dict:
        """
        Create a new checklist on a card.
    
        Args:
            card_id (str): The ID of the card to create the checklist on
            name (str): The name of the checklist
            pos (Optional[str]): The position of the checklist (top, bottom, or a positive number)
    
        Returns:
            Dict: The created checklist data
        """
        return await service.create_checklist(card_id, name, pos)
  • Registration of checklist tools including create_checklist in the MCP tool registry.
    # Checklist Tools
    mcp.add_tool(checklist.get_checklist)
    mcp.add_tool(checklist.get_card_checklists)
    mcp.add_tool(checklist.create_checklist)
    mcp.add_tool(checklist.update_checklist)
    mcp.add_tool(checklist.delete_checklist)
    mcp.add_tool(checklist.add_checkitem)
    mcp.add_tool(checklist.update_checkitem)
    mcp.add_tool(checklist.delete_checkitem)
  • ChecklistService method implementing the core logic: constructs payload and calls Trello API to create checklist.
    async def create_checklist(
        self, card_id: str, name: str, pos: str | None = None
    ) -> Dict:
        """
        Create a new checklist on a card.
    
        Args:
            card_id (str): The ID of the card to create the checklist on
            name (str): The name of the checklist
            pos (Optional[str]): The position of the checklist (top, bottom, or a positive number)
    
        Returns:
            Dict: The created checklist data
        """
        data = {"name": name}
        if pos:
            data["pos"] = pos
        return await self.client.POST(f"/checklists", data={"idCard": card_id, **data})
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. It mentions the tool creates a checklist and returns data, but doesn't disclose behavioral traits like permissions required, whether it's idempotent, error handling, or rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 well-structured and front-loaded with the core purpose, followed by clear sections for arguments and returns. Every sentence earns its place with no redundant information, making it efficient and easy to parse.

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 complexity (a mutation with 3 parameters), lack of annotations, and no output schema, the description is minimally adequate. It covers the basic purpose and parameters but lacks details on behavioral context, error cases, or return value structure, leaving gaps for an AI agent to infer.

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 adds basic semantics for all three parameters (e.g., 'card_id' is for the card to create the checklist on, 'name' is the checklist name, 'pos' specifies position options), which compensates for the 0% schema description coverage. However, it doesn't provide detailed examples or constraints beyond what's implied, such as format for 'pos' values or length limits for 'name'.

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 ('Create a new checklist') and the target resource ('on a card'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'add_checkitem' or 'create_card', which would require more context about when to use each.

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 like 'add_checkitem' (for adding items to an existing checklist) or 'create_card' (for creating a card first). It also lacks information about prerequisites, such as needing an existing card, though this is implied by the 'card_id' parameter.

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