Skip to main content
Glama
m0xai

Trello MCP Server with Python

by m0xai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_card_checklists

Retrieve all checklists for a specific Trello card to manage tasks and track progress efficiently.

Instructions

Get all checklists for a specific card.

Args:
    card_id (str): The ID of the card to get checklists for

Returns:
    List[Dict]: List of checklists on the card

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_idYes

Implementation Reference

  • server/tools/checklist.py:28-38 (handler)
    The MCP tool handler function for 'get_card_checklists' that retrieves all checklists for a given card by calling the ChecklistService.
    async def get_card_checklists(card_id: str) -> List[Dict]:
    """
    Get all checklists for a specific card.

    Args:
        card_id (str): The ID of the card to get checklists for

    Returns:
        List[Dict]: List of checklists on the card
    """
    return await service.get_card_checklists(card_id)
  • server/tools/tools.py:32-32 (registration)
    Registers the 'get_card_checklists' tool with the MCP server.
    mcp.add_tool(checklist.get_card_checklists)
  • server/services/checklist.py:29-39 (helper)
    The underlying service implementation that performs the actual Trello API call to fetch checklists for the card.
    async def get_card_checklists(self, card_id: str) -> List[Dict]:
    """
    Get all checklists for a specific card.

    Args:
        card_id (str): The ID of the card to get checklists for

    Returns:
        List[Dict]: List of checklists on the card
    """
    return await self.client.GET(f"/cards/{card_id}/checklists")

Tool Definition Quality

A3.7/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 the tool retrieves data ('Get all checklists'), implying a read-only operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error conditions, or whether it returns partial/full data. The description is minimal and lacks essential operational 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 front-loaded with the core purpose in the first sentence, followed by structured Args and Returns sections. Every sentence earns its place by providing essential information without redundancy, making it highly efficient and well-organized.

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 is adequate but has gaps. It covers the basic purpose and parameter semantics but lacks behavioral details and usage guidelines. For a read operation with minimal structured data, it meets minimum viability but could be more informative.

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 'card_id' by explaining it's 'The ID of the card to get checklists for,' which clarifies its purpose beyond the schema's basic title. With 0% schema description coverage and only one parameter, this compensation is effective, though it doesn't detail 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 ('Get all checklists') and target resource ('for a specific card'), using a precise verb+resource combination. It distinguishes itself from sibling tools like 'get_checklist' (singular) by specifying it retrieves multiple checklists associated with a card.

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 context by specifying it's for 'a specific card,' but doesn't explicitly state when to use this tool versus alternatives like 'get_checklist' or other card-related tools. No guidance is provided on prerequisites, exclusions, or comparative scenarios with siblings.

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