Skip to main content
Glama
m0xai

Trello MCP Server with Python

by m0xai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

delete_checkitem

Remove specific items from Trello checklists to maintain organized task tracking and project management workflows.

Instructions

Delete a checkitem from a checklist.

Args:
    checklist_id (str): The ID of the checklist containing the item
    checkitem_id (str): The ID of the checkitem to delete

Returns:
    Dict: The response from the delete operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checklist_idYes
checkitem_idYes

Implementation Reference

  • server/tools/checklist.py:129-140 (handler)
    The MCP tool handler function for deleting a checkitem. It delegates to the ChecklistService's delete_checkitem method.
    async def delete_checkitem(checklist_id: str, checkitem_id: str) -> Dict:
    """
    Delete a checkitem from a checklist.

    Args:
        checklist_id (str): The ID of the checklist containing the item
        checkitem_id (str): The ID of the checkitem to delete

    Returns:
        Dict: The response from the delete operation
    """
    return await service.delete_checkitem(checklist_id, checkitem_id)
  • server/tools/tools.py:38-38 (registration)
    Registration of the 'delete_checkitem' tool with the MCP server in the register_tools function.
    mcp.add_tool(checklist.delete_checkitem)
  • server/services/checklist.py:151-164 (helper)
    The ChecklistService method that performs the actual Trello API DELETE request to remove the checkitem.
    async def delete_checkitem(self, checklist_id: str, checkitem_id: str) -> Dict:
    """
    Delete a checkitem from a checklist.

    Args:
        checklist_id (str): The ID of the checklist containing the item
        checkitem_id (str): The ID of the checkitem to delete

    Returns:
        Dict: The response from the delete operation
    """
    return await self.client.DELETE(
        f"/checklists/{checklist_id}/checkItems/{checkitem_id}"
    )

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a delete operation, implying destructive behavior, but doesn't disclose critical details like whether deletion is permanent, requires specific permissions, has side effects (e.g., affecting checklist completion), or error conditions. For a destructive tool with zero annotation coverage, this is a significant gap in behavioral context.

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 highly concise and well-structured: a clear purpose statement followed by formatted Args and Returns sections. Every sentence earns its place, with no redundant or vague language. It's front-loaded with the core action.

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 (destructive operation with 2 parameters), lack of annotations, and no output schema, the description is moderately complete. It covers the purpose and parameters but lacks behavioral details (e.g., deletion consequences) and return value specifics. For a delete tool, more context on safety and outcomes would be beneficial.

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?

Schema description coverage is 0%, so the description must compensate. It explicitly lists both parameters (checklist_id and checkitem_id) with brief explanations of their roles, adding meaningful semantics beyond the bare schema. This covers all parameters adequately, though it doesn't detail format constraints (e.g., ID structure).

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 ('Delete') and target resource ('a checkitem from a checklist'), which is specific and unambiguous. It distinguishes from siblings like delete_card or delete_checklist by specifying the exact resource type. However, it doesn't explicitly contrast with alternatives like 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. It doesn't mention prerequisites (e.g., needing the checklist and checkitem IDs), exclusions, or compare with related tools like update_checkitem or delete_checklist. The agent must infer usage from context 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