Trello MCP Server

get_member_cards

List all cards assigned to a member, optionally filtered by board, to quickly see their tasks and track progress.

Instructions

Liste toutes les cartes assignées à un membre, optionnellement filtrées par 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": {
      "memberId": "<memberId>"
    },
    "name": "get_member_cards"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, but 'Liste' clearly indicates a read-only operation and 'optionnellement filtrées par board' is an explicit behavioral qualifier. However, it does not disclose pagination, whether archived cards are included, ordering, or response shape, which are relevant for a list endpoint.

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 compact sentence that leads with the main purpose and tucks the optional filter into a natural clause. No filler or redundant wording.

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 two-parameter list tool, the description is mostly complete: it identifies the required member scope and the optional board filter. The absence of an output schema and any description of the returned card fields leaves a small gap, but it is not a major obstacle to invoking the tool correctly.

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 schema already names both parameters; the tool description only maps 'un membre' to memberId and 'board' to boardId. The schema descriptions themselves are minimal ('Parameter memberId'), so the tool description adds only slightly to parameter understanding.

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 uses the specific verb 'Liste' with a clear resource, 'cartes assignées à un membre', and adds an optional board filter. This makes the tool distinguishable from sibling card tools like list_trello_cards or search_trello_cards, which are not scoped to a member's assigned cards.

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?

The description states what the tool does but gives no guidance on when to choose it over alternatives such as list_trello_cards, get_card_details, or search_trello_cards. No conditions, exclusions, or prerequisite steps are mentioned.

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

Deploy Server