Skip to main content
Glama

trello_get_member

Retrieve Trello member details including profile information, boards, and organizations to manage team collaboration and access user data.

Instructions

Get details about a specific Trello member/user, including their boards and profile information.

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)
memberIdYesID or username of the member to retrieve (use "me" for current user)
fieldsNoOptional: specific fields to include (e.g., ["fullName", "username", "bio", "url"])
boardsNoInclude member's boards in responseopen
organizationsNoInclude member's organizations in responseall

Implementation Reference

  • Handler function for the 'trello_get_member' tool.
    export async function handleTrelloGetMember(args: unknown) {
      try {
        const { apiKey, token, memberId, fields, boards, organizations } = validateGetMember(args);
        const client = new TrelloClient({ apiKey, token });
        
        const response = await client.getMember(memberId, {
          ...(fields && { fields }),
          ...(boards && { boards }),
          ...(organizations && { organizations })
        });
        const member = response.data;
        
        const result = {
          summary: `Member: ${member.fullName || member.username}`,
          member: {
            id: member.id,
            fullName: member.fullName,
            username: member.username,
            bio: member.bio,
            url: member.url,
            memberType: member.memberType,
            confirmed: member.confirmed,
            avatarUrl: member.avatarUrl,
            initials: member.initials
          },
          boards: member.boards?.map((board: any) => ({
            id: board.id,
            name: board.name,
            description: board.desc || 'No description',
            url: board.shortUrl,
            closed: board.closed,
            lastActivity: board.dateLastActivity
          })) || [],
          organizations: member.organizations?.map((org: any) => ({
            id: org.id,
            name: org.name,
            displayName: org.displayName,
            description: org.desc
          })) || [],
          rateLimit: response.rateLimit
        };
        
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof z.ZodError 
          ? formatValidationError(error)
          : error instanceof Error 
            ? error.message 
            : 'Unknown error occurred';
            
        return {
          content: [
            {
              type: 'text' as const,
              text: `Error getting member: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
    }
  • Validation schema for the input arguments of the tool.
    const validateGetMember = (args: unknown) => {
      const schema = z.object({
        apiKey: z.string().min(1, 'API key is required'),
        token: z.string().min(1, 'Token is required'),
        memberId: z.string().min(1, 'Member ID is required'),
        fields: z.array(z.string()).optional(),
        boards: z.string().optional(),
        organizations: z.string().optional()
      });
      
      return schema.parse(args);
    };
  • Tool registration definition for 'trello_get_member'.
    export const trelloGetMemberTool: Tool = {
      name: 'trello_get_member',
      description: 'Get details about a specific Trello member/user, including their boards and profile information.',
      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)'
          },
          memberId: {
            type: 'string',
            description: 'ID or username of the member to retrieve (use "me" for current user)',
            minLength: 1
          },
          fields: {
            type: 'array',
            items: { type: 'string' },
            description: 'Optional: specific fields to include (e.g., ["fullName", "username", "bio", "url"])'
          },
          boards: {
            type: 'string',
            enum: ['all', 'open', 'closed', 'none'],
            description: 'Include member\'s boards in response',
            default: 'open'
          },
          organizations: {
            type: 'string',
            enum: ['all', 'none'],
            description: 'Include member\'s organizations in response',
            default: 'all'
          }
        },
        required: ['apiKey', 'token', 'memberId']
      }
    };
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets details' which implies a read-only operation, but doesn't mention authentication requirements (though parameters suggest it), rate limits, error conditions, or what happens with invalid member IDs. The description is minimal and lacks important behavioral context for a tool with authentication parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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. It could be slightly more structured by separating the 'what' from the 'includes', but it's appropriately sized with no wasted words.

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?

Given 6 parameters (including authentication parameters), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks guidance on usage context, behavioral details, and output format. For a tool with authentication requirements and multiple configuration options, more completeness would be expected.

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 documents all 6 parameters thoroughly. The description mentions 'including their boards and profile information' which aligns with the 'boards' and 'fields' parameters, but doesn't add meaningful semantic context beyond what's in the schema. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 verb ('Get') and resource ('details about a specific Trello member/user'), including what information is retrieved ('boards and profile information'). It distinguishes from sibling tools like 'trello_get_board_members' (which gets members of a board) and 'trello_get_user_boards' (which gets boards for a user), but doesn't explicitly mention these distinctions.

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 like 'trello_get_user_boards' or 'trello_get_board_members'. It mentions retrieving member details including boards, but doesn't specify scenarios where this is preferred over other tools or any prerequisites beyond the required parameters.

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