Trello MCP

get_lists

Retrieve all lists from a specific Trello board to view workflow columns such as To Do, In Progress, and Done.

Instructions

Get all lists in a specific Trello board. Use this to see the workflow columns (like "To Do", "In Progress", "Done") in a 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": {
      "apiKey": "<apiKey>",
      "token": "<token>",
      "boardId": "<boardId>"
    },
    "name": "get_lists"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes	Trello API token (automatically provided by Claude.app from your stored credentials)
`apiKey`	Yes	Trello API key (automatically provided by Claude.app from your stored credentials)
`filter`	No	Filter lists by status: "open" for active lists, "closed" for archived lists, "all" for both	open
`boardId`	Yes	The ID of the board to get lists from (you can get this from list_boards)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full transparency burden. However, it states 'Get all lists' without mentioning that the default filter is 'open', which could mislead an agent into expecting closed lists. It also doesn't explicitly state that this is a read-only operation (though implied by 'Get'), but the filter ambiguity is a more significant gap.

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 sentence that is front-loaded with purpose and includes a helpful illustrative use case. No waste.

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?

The tool is simple and the schema covers all parameters, but the description omits the default filter behavior and return format. The phrase 'all lists' conflicts with the default 'open' filter, leaving an agent uncertain about expected results. This is a notable completeness gap given no output schema is provided.

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 each parameter described independently. The description adds no additional parameter-specific details, so it relies fully on the schema. Baseline 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?

The description clearly states the tool retrieves lists from a Trello board, with a specific verb ('Get'), resource ('lists'), and scope ('in a specific Trello board'). It also provides a concrete use case (seeing workflow columns), distinguishing it from sibling tools like get_board_details or trello_get_list_cards.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use it to see workflow columns in a board, giving clear when-to-use context. It doesn't mention alternatives or exclusions, but the use case is sufficient for this simple listing tool.

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