Trello MCP Server

Update Checklist Item

update_checklist_item

Update any Trello checklist item by marking it complete or incomplete, renaming it, or moving it to a new position. Resolve checklist inaccuracies directly from the card.

Instructions

Update a checklist item (toggle complete/incomplete, rename, or reposition).

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

Input Schema

Name	Required	Description
`pos`	No	New position
`name`	No	New name for the item
`state`	No	Set item state
`cardId`	Yes	The ID of the card containing the checklist
`checkItemId`	Yes	The ID of the check item

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does reveal the concrete mutation types (state toggle, rename, reposition), which is helpful. However, it does not disclose whether updates are partial, whether multiple fields can be updated at once, permission requirements, reversibility, or what the response contains.

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, focused sentence with a compact parenthetical that lists all supported update modes. There is no redundant wording or unnecessary background information.

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

Completeness3/5

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

The description is adequate for a simple mutation tool: all parameters are documented in the schema and the description captures the three kinds of updates. However, it lacks usage guidance, behavioral caveats, and any note about return values, which would make it more complete for an agent operating without annotations or an output schema.

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 adds a useful mapping of operations to parameters (toggle -> state, rename -> name, reposition -> pos), but it does not add meaning beyond what the schema already documents for each parameter.

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 uses a specific verb ('Update') with a specific resource ('a checklist item') and enumerates the exact operations supported: toggle complete/incomplete, rename, or reposition. This clearly distinguishes it from sibling tools like add_checklist_item, delete_checklist_item, and update_checklist.

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 implies this tool is used to modify an existing checklist item, but it does not explicitly state when to use it versus alternatives such as add_checklist_item for creating items or delete_checklist_item for removing them. No exclusions or decision guidance are provided.

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

Deploy Server