Skip to main content
Glama
Sign In
Trello MCP

Trello MCP

by brainquiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete Checklist Item

delete_checklist_item

Remove a checklist item from a Trello card by specifying the card ID and checklist item ID.

Instructions

Delete a checklist item from a card

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": "delete_checklist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYesID of the card containing the checklist item
checkItemIdYesID of the checklist item to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 carries the full behavioral burden. It indicates deletion but does not disclose irreversibility, permission requirements, side effects on the card or checklist, or what the operation returns, leaving important destructive-action context missing.

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?

The description is a single short sentence, front-loaded with the action and resource. It is not verbose, though it is also quite minimal for a delete operation.

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 destructive mutation with no annotations and no output schema, the description is incomplete. It does not mention reversibility, permissions, side effects, or error behavior, so an agent lacks enough context to invoke it safely beyond the basic operation.

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 schema documents both cardId and checkItemId clearly. The description adds no additional parameter meaning beyond the schema, so the baseline score of 3 is appropriate.

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 verb ('Delete') and resource ('checklist item from a card'), so the core operation is clear. However, it does not explicitly distinguish itself from sibling tools such as add_checklist_item or update_checklist_item, so it falls short of the highest clarity tier.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The implied usage is obvious from the verb, but no explicit context is provided.

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