Trello MCP Server

get_cards_by_list_id

Fetch cards from a specific Trello list using its list ID, with an optional board ID for precise targeting.

Instructions

Fetch cards from a specific Trello list on a specific board

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listId": "<listId>"
    },
    "name": "get_cards_by_list_id"
  }
}

Input Schema

Name	Required	Description	Default
`boardId`	No	ID of the Trello board (uses default if not provided)
`listId`	Yes	ID of the Trello list

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4May 30, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It states read-only fetch but does not disclose behavioral traits such as pagination, sorting, error handling, or what happens when boardId is omitted (default board).

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?

Single sentence, front-loaded with action and resource, no wasted words. Efficient and clear.

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 no output schema, description should clarify return format, but it does not. For a simple fetch tool, this is adequate but could be more complete by noting output structure or listing default behavior.

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?

Schema coverage is 100% with clear parameter descriptions. Description does not add additional semantics beyond what the schema already provides, so baseline score of 3 is appropriate.

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?

Description clearly states verb ('Fetch'), resource ('cards from a specific Trello list on a specific board'), and distinguishes from sibling tools like add_card_to_list or archive_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?

Description implies usage when you need cards from a list but lacks explicit when-to-use or when-not-to-use guidance. No alternatives mentioned, though context is implicit from sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.