Trello MCP Server

Get Member Boards

get_member_boards

Retrieve all Trello boards a member belongs to. Use 'me' for the authenticated user and apply filters such as open, closed, starred, or organization.

Instructions

Get all boards a member belongs to. Use 'me' for the authenticated user.

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_boards"
  }
}

Input Schema

Name	Required	Description	Default
`filter`	No	Filter boards (default: all)
`memberId`	Yes	The ID or username of the member (use 'me' for yourself)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

There are no annotations, so the description is the sole source of behavioral context. 'Get' clearly signals a read operation and 'all boards' scopes the results, but the description does not mention authentication needs, default filtering behavior, or any pagination/response details. This is adequate but not rich.

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 short sentences with no filler. The core action is front-loaded, and the 'Use me' instruction is useful and directly actionable. It is appropriately sized for a tool with only two parameters.

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 read operation with no output schema, the description plus the schema is largely sufficient to invoke the tool correctly. It could strengthen sibling differentiation and mention return format, but no critical information for a basic call is missing.

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?

The input schema already documents both parameters with 100% coverage, including the filter enum and the 'me' convention for memberId. The description reinforces the 'me' usage but does not add substantive information beyond what the schema already provides.

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 clearly states the action ('Get') and the specific resource ('all boards a member belongs to'), and it clarifies how to target the authenticated user with 'me'. It does not explicitly distinguish itself from sibling tools like list_boards or get_organization_boards, but the member-scoped purpose is clear.

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 description gives a direct usage tip for 'me' and implies the tool is for member-scoped board lookups. However, it does not state when to prefer this over alternatives such as list_boards or get_organization_boards, and it provides no exclusions or when-not-to-use guidance.

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

Deploy Server