Trello MCP Server

tre__get_cards

Retrieve all cards from a specific Trello list by providing the list ID to manage and organize tasks.

Instructions

Get all cards in a list

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": "tre__get_cards"
  }
}

Input Schema

Name	Required	Description	Default
`listId`	Yes	The ID of the list

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 26, 2026

TDQS

C2.9/5.0

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 states the action is to 'Get' cards, implying a read-only operation, but doesn't clarify aspects like whether it returns all cards at once (e.g., pagination behavior), error handling for invalid list IDs, or performance considerations. This leaves significant gaps in understanding how the tool behaves.

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 a single, clear sentence with no wasted words. It's front-loaded with the core purpose, making it efficient and easy to parse, which is ideal for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the return value looks like (e.g., an array of card objects), error conditions, or how it interacts with siblings. Given the complexity of a read operation with one required parameter, more context is needed to be complete.

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 input schema has 100% description coverage, with the 'listId' parameter clearly documented. The description doesn't add any additional meaning beyond what the schema provides, such as explaining the format of the list ID or how to obtain it. Given the high schema coverage, a baseline score of 3 is appropriate.

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 ('Get') and resource ('all cards in a list'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'tre__get_boards' or 'tre__get_lists' beyond specifying the resource type, which prevents 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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention whether this is for retrieving all cards in bulk versus using 'tre__update_card' for specific ones, or if there are prerequisites like needing a list ID from 'tre__get_lists' first.

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

Deploy Server