Skip to main content
Glama
Sign In
Trello MCP

Trello MCP

by brainquiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update Checklist Item

update_checklist_item

Modify a Trello checklist item's text, completion state, order, due date, reminder, or assigned member by card and item ID.

Instructions

Update a checklist item name, state, position, due date, reminder, or assigned member

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

NameRequiredDescriptionDefault
dueNoNew due date for the checklist item in ISO 8601 format, or null to clear it
posNoNew position for the checklist item
nameNoNew text for the checklist item
stateNoNew state for the checklist item
cardIdYesID of the card containing the checklist item
idMemberNoMember ID to assign to the checklist item, or null to clear it
checkItemIdYesID of the checklist item to update
dueReminderNoReminder offset in minutes before due date, or null to clear it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 full behavioral burden. It does not disclose mutation semantics such as partial updates, permission requirements, or what happens to fields not mentioned—only the list of updatable fields.

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?

A single, front-loaded sentence with no filler. It is appropriately sized for a simple update tool, though it could be slightly more structured by grouping required parameters.

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 an 8-parameter mutation tool with no annotations and no output schema, the description is far too sparse. It omits required parameters, update semantics, and side effects, leaving significant gaps for correct invocation.

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 schema already documents all 8 parameters thoroughly. The description merely restates the parameter names in prose and adds no new syntactic or format details, so baseline 3 applies.

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?

States a specific verb ('Update') and resource ('checklist item'), and enumerates the fields it can change. It is clearly distinct from sibling tools like add_checklist_item or delete_checklist_item.

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, no prerequisites, and no exclusions. The description only states what it does, leaving the agent to infer context.

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

Deploy Server

Other Tools