Trello MCP Server

remove_member_from_card

Unassigns a member from a Trello card with card ID and member ID. Fix incorrect card assignments.

Instructions

Retire l'assignation d'un membre d'une carte Trello

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>",
      "memberId": "<memberId>"
    },
    "name": "remove_member_from_card"
  }
}

Input Schema

Name	Required	Description	Default
`cardId`	Yes	Parameter cardId (24 characters)
`memberId`	Yes	Parameter memberId (24 characters)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 6, 2026

TDQS

C2.6/5.0

Behavior1/5

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

The description only states the action and nothing else. With no annotations provided, the description carries the full burden of behavioral disclosure, but it does not reveal whether the operation is idempotent, what happens if the member is not assigned, or any side effects such as changes to card history.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words. However, it is so minimal that it adds little beyond the tool name, making it efficient but not strongly informative.

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

Completeness2/5

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

For a simple tool with no annotations and no output schema, the description is incomplete. It does not explain the operation's effect, any constraints, or when it should be used, so an agent would have to rely almost entirely on the tool name and sibling tools for context.

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 adds no parameter semantics beyond what the schema already provides; it does not even clarify that cardId identifies the Trello card and memberId identifies the member, though these are inferable from the tool name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Retire') and resource ('l'assignation d'un membre d'une carte Trello'), clearly indicating the removal of a member assignment from a card. It is distinguishable from siblings like add_member_to_card because it describes the reverse operation.

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 such as bulk_assign_member or add_member_to_card. It does not mention prerequisites like the member needing to be currently assigned, nor any context that would help an agent decide between this and other member-related tools.

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

Deploy Server