Trello MCP

move_card

Move a card to another list to change its status (e.g., 'To Do' to 'In Progress'). Specify card ID, destination list ID, and optional position.

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": {
      "apiKey": "<apiKey>",
      "token": "<token>",
      "cardId": "<cardId>",
      "idList": "<idList>"
    },
    "name": "move_card"
  }
}

Input Schema

Name	Required	Description
`pos`	No	Position in the destination list: "top", "bottom", or specific number
`token`	Yes	Trello API token (automatically provided by Claude.app from your stored credentials)
`apiKey`	Yes	Trello API key (automatically provided by Claude.app from your stored credentials)
`cardId`	Yes	ID of the card to move (you can get this from board details or card searches)
`idList`	Yes	ID of the destination list (you can get this from get_lists)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It fails to mention potential side effects, default position behavior if pos is omitted, permission requirements, or the shape of the response. As a mutation tool, this lack of detail is a significant gap.

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 two sentences long, front-loaded with the core action, and includes a helpful example. Every word earns its place with no fluff.

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 description and schema cover the basics, but the lack of annotations and output schema leaves gaps around operational behavior (e.g., default position, idempotency, return value). The example is helpful but does not fully compensate for missing behavioral details.

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 baseline is 3. The description does not add parameter-specific meaning beyond what the schema already provides, but the schema itself is descriptive (e.g., explaining how to obtain ids).

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 tool's function with a specific verb and resource: 'Move a card to a different list.' It also provides an example of workflow status change, distinguishing this from sibling tools like update_card or create_card.

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 explicitly states when to use the tool: 'Use this to change a card's workflow status.' It provides a clear use case without explicitly listing alternatives, which is acceptable for a single-purpose action.

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