Skip to main content
Glama

list_boards

Read-only

Retrieve the current Trello user's boards, with optional open, closed, or all status filtering.

Instructions

List the boards of the current Trello user.

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

NameRequiredDescriptionDefault
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
filterNoopen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the user-scoping detail; it says nothing about pagination, result ordering, how many boards are returned, or whether archived boards appear by default despite the filter parameter existing. That leaves real behavioral gaps for a listing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded, contains no filler, and is trivially parseable. However, the brevity reads as under-specification rather than disciplined economy for a tool with a filter and a language parameter.

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?

This is a low-complexity, zero-required-parameter, read-only tool with no output schema, so the description does not need to explain return values or auth deeply. Still, with a filter parameter and a user-scoping assumption, an agent would benefit from knowing the default result set and whether it is paginated, which the definition omits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: the lang parameter is fully documented in the schema, but filter carries only an enum and a default of 'open' with no explanation of what it filters. The description supplies no parameter meaning at all, so it does not compensate for the undocumented half, and an agent gets no help on whether 'closed' or 'all' includes archived boards.

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?

States a specific verb and resource ('List the boards') plus a scope ('of the current Trello user'), so an agent knows this is a read of the caller's own boards rather than an arbitrary board lookup. It does not name or contrast with siblings like get_board or get_lists, but the verb+resource pairing is unambiguous.

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?

There is no explicit when-to-use guidance, no mention of alternatives (e.g. get_board for a single board, search for finding boards by name), and no note about when the filter values matter. Usage is only inferable from the tool name and the word 'List'.

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