Trello MCP Server

Create Checklist

create_checklist

Create a new checklist on a specified Trello card to organize tasks and subtasks.

Instructions

Create a new checklist on a Trello card.

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": {
      "cardId": "<cardId>",
      "name": "<name>"
    },
    "name": "create_checklist"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Name of the checklist
`cardId`	Yes	The ID of the card

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create' implies a write operation, but the description does not state whether the operation is idempotent, requires certain permissions, fails if the card does not exist, or has any side effects beyond adding a checklist.

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, efficient sentence with no filler. The action, resource, and target are front-loaded, making it easy for an agent to parse the essential information quickly.

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 create operation with two well-documented required parameters, no nested objects, and no output schema requirement, the description sufficiently conveys the operation and its target. However, the lack of any behavioral or usage context, given the absence of annotations, is a minor gap.

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?

Both parameters (name and cardId) are fully described in the input schema (100% coverage), so the baseline is 3. The description adds no additional meaning or usage nuance beyond what the schema already provides.

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 ('Create'), resource ('checklist'), and target ('on a Trello card'), which clearly distinguishes it from sibling tools like get_checklist, update_checklist, and delete_checklist. It is unambiguous about the operation being performed.

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 provides no guidance on when to use this tool versus alternatives such as add_checklist_item or update_checklist. It simply restates the obvious creation operation without any context, conditions, or exclusions.

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

Deploy Server