Skip to main content
Glama
Sign In
Trello MCP

Trello MCP

by brainquiver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Add Checklist Item

add_checklist_item

Add a new item to a Trello checklist. Provide the checklist name and item text, and optionally a card or board ID to scope the search.

Instructions

Add a new 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": {
      "text": "<text>",
      "checkListName": "<checkListName>"
    },
    "name": "add_checklist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText content of the checklist item
cardIdNoID of the card to scope checklist search to (recommended to avoid ambiguity)
boardIdNoID of the Trello board (uses default if not provided)
checkListNameYesName of the checklist to add the item to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It does not state whether this is a write operation needing permissions, whether it creates a new item or modifies existing data, or what happens on success (e.g., returns the new item). For a mutation tool, this is insufficient.

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

Conciseness3/5

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

The description is a single sentence that is concise but overly brief. It is front-loaded but lacks necessary detail, making it minimally viable rather than optimally informative.

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?

Given a mutation tool with four parameters, no annotations, and no output schema, the description should provide more context about behavior, permissions, or return values. It fails to address these gaps, leaving the agent under-informed.

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 four parameters thoroughly. The description adds no additional meaning beyond what is in 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 (add) and resource (checklist item), clearly distinguishing it from siblings like update_checklist_item or create_checklist. However, it doesn't specify which checklist context (e.g., requires a checklist name or card ID) or mention its relation to other checklist tools, leaving some ambiguity about scope.

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 explicit guidance on when to use this tool versus alternatives such as create_checklist or update_checklist_item. No exclusions or prerequisites are mentioned, so an agent must infer usage from context alone.

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