Skip to main content
Glama

unassign_member

Remove a member from a Trello card while keeping them on the board. Use it to unassign someone without removing their board access.

Instructions

Remove a member from a card (they stay on the 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>",
      "memberId": "<memberId>"
    },
    "name": "unassign_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
cardIdYes
memberIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation/safety profile is covered structurally. The description adds genuinely useful context that the operation is scoped to the card and does not remove board membership, but says nothing about required permissions, behavior when the member isn't on the card, or whether the action 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?

A single sentence with the key scope qualifier front-loaded in parentheses; every word earns its place and there is no redundancy with the name.

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 simple three-parameter mutation with annotations covering the safety hints and no output schema, the definition covers purpose and scope adequately. Minor gaps remain around failure modes (member not on card, missing permissions) that an agent might want to anticipate.

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 only 33% — only 'lang' is documented (with a strong 'always pass it' note); cardId and memberId have no descriptions. The description adds nothing about the parameters, though the two undocumented names are self-explanatory identifiers, which keeps this at a baseline 3 rather than lower.

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 and resource ('Remove a member from a card') and adds scope clarification '(they stay on the board)' that immediately distinguishes it from the board-level sibling remove_member_from_board. An agent can select it without opening 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 Guidelines3/5

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

The parenthetical implies the when-to-use condition (card-level unassignment rather than board removal), but the description never explicitly says when to prefer it over assign_member or remove_member_from_board, nor states prerequisites such as needing the member to be assigned first.

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