trello-mcp

Add an item to a checklist

add_checklist_item

Add a new check item to an existing Trello checklist. Specify the text, optionally set its position and checked status.

Instructions

Add a check item to a 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": {
      "idChecklist": "<idChecklist>",
      "name": "<name>"
    },
    "name": "add_checklist_item"
  }
}

Input Schema

Name	Required	Description
`pos`	No	Position: "top", "bottom", or a positive number
`name`	Yes	Check item text
`checked`	No	Create the item already checked
`idChecklist`	Yes	Checklist id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jul 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only says 'add'. It does not disclose side effects, permissions, or what happens with duplicate names – minimal behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no wasted words. However, it is too sparse; a bit more detail would not harm conciseness.

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?

No output schema, so description should clarify return value or state changes. It does not. For a tool with 4 parameters and no behavioral notes, it feels incomplete.

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 coverage is 100%, so baseline is 3. The description adds no extra meaning beyond 'check item', repeating the parameter name 'name'. No additional context for optional parameters like 'pos' or 'checked'.

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 ('Add') and resource ('check item to a checklist'), matching the title. However, it does not differentiate from sibling tools like 'create_checklist' which creates a checklist itself.

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?

No guidance on when to use this tool versus alternatives. The description is too brief to provide any usage context or exclusions.

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