Skip to main content
Glama

trello_get_board_members

Retrieve all members with access to a specific Trello board to manage team collaboration and permissions.

Instructions

Get all members who have access to a specific Trello board.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesTrello API key (automatically provided by Claude.app from your stored credentials)
tokenYesTrello API token (automatically provided by Claude.app from your stored credentials)
boardIdYesID of the board to get members for

Implementation Reference

  • The handler function that executes the Trello get board members tool logic.
    export async function handleTrelloGetBoardMembers(args: unknown) {
      try {
        const { apiKey, token, boardId } = validateGetBoardMembers(args);
        const client = new TrelloClient({ apiKey, token });
        
        const response = await client.getBoardMembers(boardId);
        const members = response.data;
        
        const result = {
          summary: `Found ${members.length} member(s) on board`,
          boardId,
          members: members.map(member => ({
            id: member.id,
            fullName: member.fullName,
            username: member.username,
            memberType: member.memberType,
            confirmed: member.confirmed,
            avatarUrl: member.avatarUrl,
            initials: member.initials
          })),
          rateLimit: response.rateLimit
        };
        
        return {
          content: [
            {
  • The tool registration and input schema definition for trello_get_board_members.
    export const trelloGetBoardMembersTool: Tool = {
      name: 'trello_get_board_members',
      description: 'Get all members who have access to a specific Trello board.',
      inputSchema: {
        type: 'object',
        properties: {
          apiKey: {
            type: 'string',
            description: 'Trello API key (automatically provided by Claude.app from your stored credentials)'
          },
          token: {
            type: 'string',
            description: 'Trello API token (automatically provided by Claude.app from your stored credentials)'
          },
          boardId: {
            type: 'string',
            description: 'ID of the board to get members for',
            pattern: '^[a-f0-9]{24}$'
          }
        },
        required: ['apiKey', 'token', 'boardId']
      }
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves members but doesn't describe what 'members' includes (e.g., roles, permissions, user details), whether it's paginated, rate limits, authentication needs (implied by parameters but not explained), or error conditions. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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, efficient sentence that front-loads the core purpose ('Get all members who have access to a specific Trello board'). There is no wasted text, repetition, or unnecessary elaboration, making it easy to parse quickly.

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?

Given the lack of annotations and output schema, the description is incomplete for a tool that retrieves data. It doesn't explain what the output contains (e.g., member details, structure), potential limitations, or error handling. While the schema covers inputs well, the overall context for an agent to use this tool effectively is insufficient.

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%, with clear documentation for all three parameters (apiKey, token, boardId). The description adds no parameter-specific information beyond implying 'boardId' is needed, which is already covered by the schema. This meets the baseline of 3 since the schema does the heavy lifting, but the description doesn't enhance parameter understanding.

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 all members') and resource ('who have access to a specific Trello board'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'trello_get_member' (singular) and 'get_board_details', though it doesn't explicitly contrast with them. The description is specific but could be more precise about distinguishing from similar tools.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing board access), compare it to similar tools like 'trello_get_member' or 'get_board_details', or indicate scenarios where this is the appropriate choice. The agent must infer usage from the name and description alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kocakli/Trello-Desktop-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server