Trello MCP Server

Get Checklist

get_checklist

Fetch a complete checklist using its ID, including all its items, to quickly inspect task lists and details.

Instructions

Get a checklist by ID, including all its items.

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": {
      "checklistId": "<checklistId>"
    },
    "name": "get_checklist"
  }
}

Input Schema

Name	Required	Description	Default
`checklistId`	Yes	The ID of the checklist

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly communicates that this is a retrieval operation and that the response includes all checklist items, which is valuable given there is no output schema. It does not cover edge cases like not-found behavior or permissions, but the core behavior of a simple getter is transparent enough.

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 front-loaded sentence with no filler. It names the action, the target, and the key return detail in minimal words, so every part earns its place.

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?

With no output schema, the phrase 'including all its items' is important and helps set return expectations. Given that the tool has only one required parameter and simple read semantics, this is mostly complete, though error behavior is not mentioned.

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% for the single parameter, and the schema already explains that checklistId is 'The ID of the checklist'. The description's 'by ID' only rephrases this without adding format, source, or other semantic detail. Baseline 3 applies because the schema does the heavy lifting.

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?

The description states a specific verb ('Get') and resource ('checklist by ID'), and explicitly notes that the result includes all items. This makes it clearly distinguishable from related siblings like create_checklist, update_checklist, and get_list without needing to inspect schemas.

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 guidance about when to use this tool instead of alternatives. It does not say that this is the read-only lookup option, nor does it point to create_checklist, update_checklist, or add_checklist_item for mutations. The use case must be inferred from the tool name and the verb 'Get'.

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

Deploy Server