Trello MCP Server

bulk_move_cards

Move multiple Trello cards to a single list at once by specifying card IDs and target list, with optional position.

Instructions

Déplace plusieurs cartes vers une liste en une fois

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": {
      "cardIds": "<cardIds>",
      "targetListId": "<targetListId>"
    },
    "name": "bulk_move_cards"
  }
}

Input Schema

Name	Required	Description
`cardIds`	Yes	Parameter cardIds
`position`	No	Parameter position
`targetListId`	Yes	Parameter targetListId (24 characters)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 6, 2026

TDQS

A3.5/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 burden of behavioral disclosure. It only states the basic move action and batching, but does not mention permissions, reversibility, partial-failure behavior, or effects on card positions beyond the optional 'position' parameter.

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 short sentence with no filler. It front-loads the action, object, destination, and batching intent, making it easy to parse quickly.

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 core invocation details are covered by the description and schema: required cardIds and targetListId, plus optional position. However, for a mutating bulk operation with no annotations and no output schema, it lacks behavioral context such as atomicity or what happens to the source lists.

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 coverage is 100%, so the baseline applies. The description adds some semantic value by linking 'plusieurs cartes' to cardIds and 'une liste' to targetListId, but it does not clarify the 'position' parameter or enforce the ID format beyond what the schema already states.

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 ('Déplace'), identifies the resource ('plusieurs cartes'), and states the destination ('vers une liste') plus the batching aspect ('en une fois'). This clearly distinguishes it from single-card move_trello_card and bulk_archive_cards.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrasing implies the tool is for moving multiple cards in one batch, and the sibling set includes move_trello_card for single-card moves. However, it does not explicitly name alternatives or state when not to use this tool, so the routing is left to inference.

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

Deploy Server