Retrieve all lists from a specified board to view and manage task columns.
List lists in a board
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": "listLists"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| boardId | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden but fails to disclose any behavioral traits. It does not state that the tool is read-only, what happens on invalid input, or any auth requirements. It only implies a read operation without explicit confirmation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise at 5 words, with no wasted text. However, it lacks structure: no sentences about usage, parameters, or returns. It sacrifices completeness for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity (1 param, no output schema), the description should hint at the return value or behavior. It does not mention what the tool outputs (e.g., list of list objects) or any error conditions, leaving the agent uninformed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0% description coverage, and the description does not explain the 'boardId' parameter beyond the vague phrase 'in a board'. No guidance is given on how to find or format the boardId.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'List lists in a board' clearly specifies the action (list) and resource (lists) with context (in a board). It distinguishes from sibling tools like listBoards and listCards, though it could be more specific about scope (e.g., 'all lists').
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidelines are provided. The description does not mention when to use this tool versus alternatives like listCards or listSwimlanes, nor any prerequisites (e.g., valid boardId).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.