Atlassian Trello MCP Server

list_boards

Retrieve all Trello boards you have access to. Filter by open, closed, or both to focus on active or archived boards.

Instructions

List all Trello boards accessible to the user. Use this to see all boards you have access to, or filter by status.

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

Input Schema

Name	Required	Description	Default
`apiKey`	No	Trello API key (optional if TRELLO_API_KEY env var is set)
`token`	No	Trello API token (optional if TRELLO_TOKEN env var is set)
`filter`	No	Filter boards by status: "open" for active boards, "closed" for archived boards, "all" for both	open

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1May 8, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description must disclose behavioral traits. It states the tool lists boards and allows filtering, but omits details on pagination, authentication requirements, or response format. The parameter schema covers auth tokens, but the description does not elaborate on behavior beyond the basic functionality.

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?

Two succinct sentences with key information front-loaded. No redundant or unnecessary wording; every word contributes to understanding.

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 list tool with three parameters and no output schema, the description covers the core functionality and usage. However, it could briefly mention the output format or that board objects are returned, which would improve completeness given the absence 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 each parameter is described. The description adds 'filter by status' which repeats the schema's enum description. No additional meaning or usage context is provided beyond what the schema already offers.

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?

Clearly states verb 'list' and resource 'boards', specifies filtering option, and distinguishes from sibling tools by focusing on listing all accessible boards.

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?

Indicates when to use the tool ('to see all boards you have access to, or filter by status'), but does not explicitly mention when not to use it or compare with sibling tools like trello_get_user_boards.

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

Deploy Server