Skip to main content
Glama
scarecr0w12

discord-mcp

get_member_info

Retrieve detailed Discord server member information using guild and user IDs to manage user data and permissions.

Instructions

Get detailed information about a specific member

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guildIdYesThe ID of the server (guild)
memberIdYesThe ID of the member (user ID)

Implementation Reference

  • Primary implementation of the get_member_info tool. This server.tool() call registers the tool, defines its input schema (guildId and memberId), and provides the handler function that uses the Discord client to fetch guild and member data, compiles comprehensive member information including roles, permissions, timestamps, and manageability flags, handles errors, and returns JSON-formatted response.
    server.tool(
      'get_member_info',
      'Get detailed information about a specific member',
      {
        guildId: z.string().describe('The ID of the server (guild)'),
        memberId: z.string().describe('The ID of the member (user ID)'),
      },
      async ({ guildId, memberId }) => {
        const result = await withErrorHandling(async () => {
          const client = await getDiscordClient();
          const guild = await client.guilds.fetch(guildId);
          const member = await guild.members.fetch(memberId);
    
          return {
            id: member.id,
            username: member.user.username,
            displayName: member.displayName,
            nickname: member.nickname,
            discriminator: member.user.discriminator,
            joinedAt: member.joinedAt?.toISOString(),
            premiumSince: member.premiumSince?.toISOString(),
            communicationDisabledUntil: member.communicationDisabledUntil?.toISOString(),
            pending: member.pending,
            isBot: member.user.bot,
            avatar: member.displayAvatarURL(),
            banner: member.user.bannerURL(),
            roles: member.roles.cache.map((r) => ({
              id: r.id,
              name: r.name,
              color: r.hexColor,
              position: r.position,
            })),
            permissions: member.permissions.toArray(),
            highestRole: {
              id: member.roles.highest.id,
              name: member.roles.highest.name,
            },
            isOwner: member.id === guild.ownerId,
            manageable: member.manageable,
            kickable: member.kickable,
            bannable: member.bannable,
            moderatable: member.moderatable,
          };
        });
    
        if (!result.success) {
          return { content: [{ type: 'text', text: result.error }], isError: true };
        }
    
        return { content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }] };
      }
    );
  • src/index.ts:56-56 (registration)
    In the createMcpServer() function, calls registerMemberTools(server) to register all member management tools including get_member_info on the MCP server instance.
    registerMemberTools(server);
  • src/index.ts:13-13 (registration)
    Imports the registerMemberTools function used to register the get_member_info tool.
    import { registerMemberTools } from './tools/member-tools.js';
  • Zod schema definition for get_member_info tool inputs: guildId and memberId as strings.
      guildId: z.string().describe('The ID of the server (guild)'),
      memberId: z.string().describe('The ID of the member (user ID)'),
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a read operation ('Get'), implying non-destructive behavior, but doesn't disclose authentication requirements, rate limits, error conditions, or what 'detailed information' includes. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 with zero waste. It's appropriately sized for a simple lookup tool and front-loads the core purpose without unnecessary elaboration.

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?

For a simple read operation with 2 parameters and 100% schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more context about what information is returned and any behavioral constraints. It meets basic needs but has clear gaps.

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 both parameters clearly documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., format of IDs, examples). Baseline 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 action ('Get detailed information') and target ('about a specific member'), which is a specific verb+resource combination. However, it doesn't distinguish this tool from similar sibling tools like 'get_server_info' or 'get_role_info' beyond the resource type, missing explicit differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. With sibling tools like 'list_members' and 'modify_member' available, the description lacks context about when detailed info retrieval is preferred over listing or when it should be used in conjunction with other tools.

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/scarecr0w12/discord-mcp'

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