Skip to main content
Glama
Sign In
Trello MCP Server

Trello MCP Server

by GabrielRamirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Move Card

move_card

Move a Trello card to a different list or board. Specify destination list, optional board, and position to reorganize workflow.

Instructions

Move a card to a different list, and optionally to a different board.

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>",
      "idList": "<idList>"
    },
    "name": "move_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
posNoPosition in the destination list
cardIdYesThe ID of the card to move
idListYesThe ID of the destination list
idBoardNoThe ID of the destination board (if moving across boards)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

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 carries the full burden of behavioral disclosure. It states the basic mutation but does not mention permissions required, whether card contents like labels and members are preserved, whether the move is reversible, or how position is applied. This is a notable gap for a mutation tool with zero annotation coverage.

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?

A single, front-loaded sentence with no filler. It names the action and both possible destinations efficiently, which is appropriately sized for a simple card move tool.

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 schema provides complete parameter documentation, but the description is thin overall. It lacks output expectations, error cases, and any behavioral cautions, and there is no output schema or annotations to compensate. For a low-complexity tool it may barely suffice, but more context would help an agent avoid mistakes when moving cards across boards.

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 fully documents all four parameters. The description adds only a slight clarification that the board change is optional, which is already implied by the schema's 'if moving across boards' note. It provides no meaningful extra parameter semantics.

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 states a specific action ('move') on a specific resource ('a card') with explicit destinations: 'to a different list, and optionally to a different board.' This clearly differentiates it from siblings like update_card and archive_card, and the singular 'a card' distinguishes it from move_all_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?

No guidance is given on when to use this tool versus alternatives. It does not mention move_all_cards for bulk moves, move_list_to_board for board-level moves, or any exclusions or prerequisites. The usage context is only implicit in the action described.

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