Skip to main content
Glama

discord_list_members

Retrieve and display Discord server members with their assigned roles using guild ID and optional limit parameters.

Instructions

List guild members with their roles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes
limitNo1–1000, default 50.

Implementation Reference

  • The handler implementation for the 'discord_list_members' tool which fetches guild members and formats their details.
    case "discord_list_members": {
      const guild = await discord.guilds.fetch(validateId(args.guild_id, "guild_id"));
      const limit = Math.min(Number(args.limit ?? 50), 1000);
      const members = await guild.members.list({ limit });
      const result = [...members.values()].map((m: GuildMember) => ({
        id: m.id, username: m.user.tag, nickname: m.nickname,
        roles: m.roles.cache.filter((r) => r.name !== "@everyone").map((r) => ({ id: r.id, name: r.name })),
        joinedAt: m.joinedAt?.toISOString(),
      }));
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • The definition and input schema for the 'discord_list_members' tool.
    {
      name: "discord_list_members",
      description: "List guild members with their roles.",
      inputSchema: {
        type: "object",
        properties: {
          guild_id: { type: "string" },
          limit: { type: "number", description: "1–1000, default 50." },
        },
        required: ["guild_id"],
      },
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states what the tool does, not behavioral traits. It doesn't disclose if it's read-only, requires permissions, has rate limits, returns paginated results, or what happens on errors, which is inadequate for a tool with potential complexity.

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, front-loading the core action. It's appropriately sized for the tool's apparent simplicity, making it easy to scan and understand 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 no annotations, no output schema, and incomplete parameter documentation, the description is insufficient. It lacks details on return format (e.g., list structure, role data), error handling, or operational constraints, leaving significant gaps for an agent to use it effectively.

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 50%, with 'limit' documented but 'guild_id' not. The description adds no parameter semantics beyond the schema, failing to explain 'guild_id' meaning or usage. Baseline is 3 due to partial schema coverage, but the description doesn't compensate for gaps.

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 ('List') and resource ('guild members'), specifying that roles are included. It distinguishes from some siblings like 'discord_get_member_info' (single member) but not from 'discord_get_role_members' (members by role), making it specific but not fully differentiated.

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 like 'discord_get_role_members' or 'discord_get_member_info'. The description lacks context about prerequisites, such as needing guild access, or exclusions, leaving usage unclear.

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

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