Skip to main content
Glama

List cards

trello_list_cards
Read-only

List open cards on a board or in a list. Use listId to narrow to a column or boardId for the whole board.

Instructions

List open cards on a board or in one list. Pass listId to narrow to a column, otherwise boardId for the whole board.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trello_list_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdNoList id; takes precedence over boardId
boardIdNoBoard id, short link, or URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a read-only, non-destructive operation. The description adds useful behavioral context by specifying that only open cards are returned and that list scoping takes precedence, but it does not cover pagination, return shape, or rate-limit behavior.

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 two tight sentences with the primary action and scoping rule front-loaded. Every sentence earns its place and there is no redundant or filler content.

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

Completeness4/5

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

For a simple read-only list tool whose annotations cover safety and whose schema fully documents parameters, the description is largely complete. It could mention pagination or return shape, but those gaps are minor given the tool's simplicity and lack of an output schema.

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%, so the schema already documents listId precedence and boardId formats. The description reinforces the scope-selection semantics but does not add syntax or format details beyond what the schema provides, making 3 the appropriate baseline.

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 gives a specific verb and resource ('List open cards') plus scope options ('on a board or in one list'). It clearly distinguishes list-scoped from board-scoped retrieval, but it does not explicitly differentiate this tool from sibling tools such as trello_search_cards or trello_get_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 explains how to scope the call ('Pass listId to narrow to a column, otherwise boardId for the whole board'), which implies usage. However, it does not say when to use this tool instead of trello_search_cards or trello_get_card, so alternative selection is left to inference.

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