Trello MCP Server

add_checklist_item

Add a new item to any existing Trello checklist. Provide the checklist ID and item name, with optional position or checked status.

Instructions

Ajoute un item à une checklist existante

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": "<name>"
    },
    "name": "add_checklist_item"
  }
}

Input Schema

Name	Required	Description
`pos`	No	Parameter pos
`name`	Yes	Parameter name
`checked`	No	Parameter checked
`checklistId`	Yes	Parameter checklistId (24 characters)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only reveals that the operation adds an item; it does not mention side effects, return values, failure handling, or what happens if the checklist does not exist.

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 communicates the core operation efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating tool with no annotations and no output schema, this description is too thin. It lacks behavioral context, alternatives, and prerequisite details, leaving an agent to infer important invocation decisions from the schema and sibling names alone.

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%, so the baseline is 3. The description does not add meaningful detail about pos or checked, though it clarifies that checklistId refers to the target checklist and name refers to the item being added.

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?

The description clearly states the action: adding an item to an existing checklist. This is distinguishable from related siblings like add_checklist_to_card or check_checklist_item, though it does not explicitly name them.

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 guidance about when to use this tool versus alternatives such as check_checklist_item or add_checklist_to_card. The word 'existante' implies a prerequisite, but there is no when-to-use or when-not-to-use guidance.

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

Deploy Server