Skip to main content
Glama

add_checklist_item

Add an item to an existing Trello checklist, with optional checked status, for task breakdowns and to-do tracking.

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

NameRequiredDescriptionDefault
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
nameYes
checkedNo
checklistIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety basics are covered. The description adds nothing beyond them: no mention of duplicate-name handling, item ordering/position, whether the item defaults to unchecked, or what is returned. For a mutation tool this is thin added context.

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 wasted words. It is efficient, though its brevity reflects under-specification rather than disciplined compression.

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?

The tool has 4 parameters at 25% schema coverage, no output schema, and mutation semantics, so the description carries a heavy burden it does not meet. An agent still lacks defaults, validation expectations, and the distinction from set_checkitem_state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% — only 'lang' is documented, while checklistId, name, and checked are bare. The description does not compensate: it never explains that checklistId must reference an existing checklist, nor what 'checked' defaults to or whether it can be omitted.

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 gives a specific verb (add) plus resource (item) and target (an existing checklist), which distinguishes it from create_checklist and delete_checklist. It stops short of naming any sibling explicitly or clarifying its relationship to set_checkitem_state, which also touches checklist items.

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 when-to-use guidance, no prerequisites stated (e.g. that the checklist must already exist vs. be created first), and no routing to alternatives. With siblings like create_checklist and set_checkitem_state present, the agent is left to infer whether item creation belongs here or there.

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