trello-mcp

Move card

trello_move_card

Move a Trello card to a different list on the same board. Provide the target list ID to relocate tasks.

Instructions

Move a card to another list on the same board. List ids come from trello_list_lists.

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>",
      "listId": "<listId>"
    },
    "name": "trello_move_card"
  }
}

Input Schema

Name	Required	Description	Default
`cardId`	Yes	Card id, short link, or the full card URL (https://trello.com/c/...)
`listId`	Yes	Target list id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 21, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is covered. The description adds one useful constraint the annotations do not carry — that the destination must be on the same board — but says nothing about side effects such as the card's resulting position or whether the operation is reversible.

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?

Two short sentences, zero filler, with the core action and the board constraint front-loaded before the id-source hint. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with no output schema and no nested objects, the description plus annotations cover what an agent needs to invoke it correctly. The only mild gap is not stating the card's resulting position in the target list, which is minor at this complexity.

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%, with cardId documenting id/short-link/URL forms and listId documented as the target list. The description only adds the provenance of listId ('from trello_list_lists'), which is marginal on top of a fully documented schema, so the baseline 3 applies.

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?

States a specific verb ('Move'), resource ('card'), destination ('another list'), and a scoping constraint ('on the same board'). No sibling in the list moves cards, so the operation is unambiguous without consulting any schema.

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

Usage Guidelines4/5

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

It routes the agent to trello_list_lists for the required listId and implicitly excludes cross-board moves via 'on the same board'. It stops short of an explicit when-not statement (e.g., how to move between boards), but the operative context is clear.

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

Deploy Server