Skip to main content
Glama
m0xai

Trello MCP Server with Python

by m0xai

add_checkitem

Add items to Trello checklists to track tasks and progress within cards.

Instructions

Add a new item to a checklist.

Args:
    checklist_id (str): The ID of the checklist to add the item to
    name (str): The name of the checkitem
    checked (bool): Whether the item is checked
    pos (Optional[str]): The position of the item

Returns:
    Dict: The created checkitem data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checklist_idYes
nameYes
checkedNo
posNo

Implementation Reference

  • MCP tool handler for 'add_checkitem'. Defines parameters via type hints and docstring, delegates to ChecklistService.
    async def add_checkitem(
        checklist_id: str, name: str, checked: bool = False, pos: str | None = None
    ) -> Dict:
        """
        Add a new item to a checklist.
    
        Args:
            checklist_id (str): The ID of the checklist to add the item to
            name (str): The name of the checkitem
            checked (bool): Whether the item is checked
            pos (Optional[str]): The position of the item
    
        Returns:
            Dict: The created checkitem data
        """
        return await service.add_checkitem(checklist_id, name, checked, pos)
  • Registers the 'add_checkitem' tool with the MCP server.
    mcp.add_tool(checklist.add_checkitem)
  • ChecklistService.add_checkitem method: constructs payload and calls Trello API to create checkitem.
    async def add_checkitem(
        self,
        checklist_id: str,
        name: str,
        checked: bool = False,
        pos: str | None = None,
    ) -> Dict:
        """
        Add a new item to a checklist.
    
        Args:
            checklist_id (str): The ID of the checklist to add the item to
            name (str): The name of the checkitem
            checked (bool): Whether the item is checked
            pos (Optional[str]): The position of the item
    
        Returns:
            Dict: The created checkitem data
        """
        data = {"name": name, "checked": checked}
        if pos:
            data["pos"] = pos
        return await self.client.POST(
            f"/checklists/{checklist_id}/checkItems", data=data
        )
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 implies a write operation ('Add a new item'), which is useful, but fails to mention critical details such as required permissions, whether the operation is idempotent, error handling, or rate limits. For a mutation tool, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and appropriately sized, with a clear purpose statement followed by parameter and return value sections. Every sentence adds value, and it avoids unnecessary verbosity. A slight improvement in front-loading key behavioral details could make it perfect.

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 moderate complexity (4 parameters, mutation operation) and lack of annotations or output schema, the description is partially complete. It covers the basic purpose and parameters but misses important contextual elements like error cases, side effects, and return value details, which are crucial for safe and effective use.

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 includes an 'Args' section that documents all four parameters with brief explanations, adding meaning beyond the input schema (which has 0% description coverage). However, it doesn't provide deeper context, such as format examples for 'checklist_id' or how 'pos' affects ordering, leaving some semantic gaps. This compensates partially but not fully for the low schema coverage.

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 tool's purpose: 'Add a new item to a checklist.' It specifies the verb ('Add') and resource ('item to a checklist'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'create_checklist' or 'update_checkitem', which would be needed for a perfect score.

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. For example, it doesn't mention when to choose 'add_checkitem' over 'create_checklist' or 'update_checkitem', nor does it specify prerequisites like needing an existing checklist. This lack of context leaves the agent without clear usage instructions.

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