Skip to main content
Glama
Sign In
Trello MCP Server

Trello MCP Server

by JulianKerignard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_board_members

Fetch all members of a Trello board with their details to see who has access and manage team assignments.

Instructions

Liste tous les membres d'un board Trello avec leurs informations

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": {
      "boardId": "<boardId>"
    },
    "name": "get_board_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdYesParameter boardId (24 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. 'Liste' clearly signals a read-only, non-mutating operation, and 'tous les membres' defines the scope of the result. It does not discuss authentication or member field details, but it avoids implying any side effects.

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 a single, front-loaded sentence with no redundant words. It states the action, the target resource, and the output in one line, making it easy for an agent to parse quickly.

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 tool is simple with one required parameter and no output schema, but the phrase 'avec leurs informations' is vague about which member fields are returned. There is no mention of result format or potential edge cases, so the description is adequate but not fully complete.

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%, and the only parameter is boardId, which is already documented as a 24-character string. The description adds no new parameter semantics beyond the implicit link to the board, so the baseline of 3 applies.

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 a specific verb ('Liste') and a clear resource ('membres d'un board Trello') with the expected result ('avec leurs informations'). No sibling tool overlaps with listing board members, so the tool's purpose is unambiguous.

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 intended use is clear: call this when you need all members of a board and their details. It does not name alternatives, but no sibling provides the same function, so the context is sufficient and there are no exclusions to state.

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

Deploy Server

Other Tools