Trello MCP Server

move_trello_card

Move a Trello card to a different list or adjust its position within the current list.

Instructions

Déplace une carte Trello vers une autre list et/ou change sa position

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>",
      "targetListId": "<targetListId>"
    },
    "name": "move_trello_card"
  }
}

Input Schema

Name	Required	Description
`cardId`	Yes	Parameter cardId (24 characters)
`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

B3.3/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 behavioral burden. It states the mutation but does not disclose side effects, permissions, reversibility, or what happens when only a position change is intended. This is a significant gap for a mutating tool.

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 concise sentence that communicates the core operation without redundancy. It is effectively front-loaded and every word contributes meaning.

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?

For a simple action, this is minimally viable: the operation and parameters are clear. However, with no annotations and no usage guidance, the description leaves out side-effect context and does not help an agent choose between this tool and the related bulk_move_cards sibling.

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 parameters. The description adds some context by linking targetListId to moving lists and position to changing position, but it does not provide details beyond the schema baseline.

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 and resource: it moves a Trello card to another list and/or changes its position. It clearly distinguishes this single-card operation from siblings like bulk_move_cards.

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?

The description implies the tool is for moving a single card, but it gives no explicit guidance on when to prefer it over alternatives such as bulk_move_cards. There are no exclusions or alternative routing cues.

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

Deploy Server