Atlassian Trello MCP Server

move_card

Change a card's workflow status by moving it to a different list, such as from To Do to In Progress.

Instructions

Move a card to a different list. Use this to change a card's workflow status (e.g., from "To Do" to "In Progress").

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

Name	Required	Description
`apiKey`	No	Trello API key (optional if TRELLO_API_KEY env var is set)
`token`	No	Trello API token (optional if TRELLO_TOKEN env var is set)
`cardId`	Yes	ID or URL of the card to move (e.g. "abc123" or "https://trello.com/c/abc123/1-title")
`idList`	Yes	ID of the destination list (you can get this from get_lists)
`pos`	No	Position in the destination list: "top", "bottom", or specific number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1May 8, 2026

TDQS

A3.8/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 full burden. It only states the basic action without disclosing side effects, permission requirements, or limitations (e.g., whether it ignores position if not specified). This is insufficient for a mutation operation.

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 sentences: the first states the primary action clearly, the second provides a concrete example. No unnecessary words, front-loaded with purpose.

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?

The description covers the core action adequately for a simple move operation. However, without an output schema, it does not explain what the tool returns (e.g., the moved card object), which could be useful for an agent. Minor gap, but overall sufficient.

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% and all parameters have descriptions. The tool description adds no extra meaning beyond the schema; it restates the purpose but does not clarify parameter values like 'pos' enum or 'cardId' format beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the action (move), resource (card), destination (list), and provides a concrete workflow status change example. It distinguishes from sibling 'update_card' by specifying moving to a different list as the primary purpose.

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?

The description gives a clear use case ('change a card's workflow status'), making it easy to know when to use it. However, it does not explicitly state when not to use it or mention alternatives like 'update_card' which might also change list along with other fields.

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

Deploy Server