Trello MCP Server

Add Checklist Item

add_checklist_item

Add new items to an existing Trello checklist by providing the checklist ID and item name. Set position or checked status to manage tasks efficiently.

Instructions

Add an item to an existing checklist.

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	Position of the item
`name`	Yes	Name/text of the checklist item
`checked`	No	Whether the item starts checked (default: false)
`checklistId`	Yes	The ID of the checklist

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

B3.2/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 behavioral disclosure burden. It only states the basic effect of adding an item and does not mention permissions, failure behavior, default item placement, or return values.

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 clear sentence with no filler. It front-loads the action and resource, and every word contributes meaning.

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?

Despite complete parameter schema coverage, the overall tool context is thin: no annotations, no output schema, and no mention of default behavior for optional parameters like 'pos' or error conditions. An agent could invoke the tool with required parameters but would lack important behavioral context.

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 input schema already documents all four parameters. The description adds no additional semantic detail beyond what the schema provides, so it sits at the baseline.

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 states a specific action and object: 'Add an item to an existing checklist.' It is not a tautology and clearly conveys the tool's intent, though it does not explicitly name or differentiate from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'existing checklist' implies a prerequisite and situates this as an add operation rather than a create or update operation. However, there is no explicit guidance about when to prefer this over alternatives like create_checklist or update_checklist_item.

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

Deploy Server