Trello MCP Server

list_boards_in_workspace

Retrieve all boards in a given Trello workspace by providing its workspace ID. This returns a list of board details for that workspace.

Instructions

List all boards in a specific workspace

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "list_boards_in_workspace"
  }
}

Input Schema

Name	Required	Description	Default
`workspaceId`	Yes	ID of the workspace to list boards from

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4May 30, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states 'list all boards' but does not mention that the operation is read-only, any authentication requirements, rate limits, or what the response contains. This is a significant gap for a tool with no annotation support.

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 unnecessary words. It front-loads the action and scope effectively.

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 the simplicity of the tool (one required param, no output schema), the description is minimally adequate. It could be improved by mentioning what the output looks like (e.g., list of board names/IDs) or whether there is pagination, but it is not critically incomplete.

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 description coverage is 100%, so the baseline is 3. The description adds the phrase 'in a specific workspace', which weakly echoes the schema's workspaceId description. It does not add new semantic meaning or constraints beyond what the schema already provides.

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 verb 'list' and the resource 'boards' scoped to a workspace. While it distinguishes from siblings like 'list_boards' (which likely lists all boards) and 'list_workspaces', it does not explicitly contrast with these alternatives.

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 implies usage when the user wants boards from a specific workspace (via workspaceId). However, it lacks explicit when-to-use or when-not-to-use guidance and does not mention alternatives like 'list_boards' for cross-workspace needs.

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