Skip to main content
Glama
Sign In
trello-mcp

trello-mcp

by Artem-Pavlenko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List lists on a board

trello_list_lists
Read-only

Fetch all open lists (columns) on a Trello board using its board ID to view workflow stages and organize cards by status.

Instructions

List the open lists (columns) of 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": {
      "boardId": "<boardId>"
    },
    "name": "trello_list_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdYesBoard id, short link, or board URL (https://trello.com/b/...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description does add one real behavioral trait beyond the schema: only OPEN lists are returned, implying archived lists are excluded. It says nothing about ordering, pagination, or permissions.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler. Efficient, though its terseness leaves the usage-guidance gap unaddressed.

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 one-parameter read tool with full schema coverage and safety annotations, the description covers what the agent needs. Only minor omissions (result ordering, whether closed lists can be requested) remain.

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% and the single boardId parameter already documents accepted forms (id, short link, or URL). The description adds no parameter detail, so the schema does the work — baseline 3.

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?

Specific verb (list) plus resource (lists/columns of a board), clearly distinct from siblings like trello_list_boards and trello_list_cards. No explicit naming of siblings, so it stops short of a 5.

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?

The description gives no when-to-use or when-not-to-use guidance, and does not point to alternatives for fetching board content (e.g. trello_list_cards). Usage is only inferable from the verb and resource.

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

Deploy Server

Other Tools