Skip to main content
Glama
Sign In
MCP-Discord

MCP-Discord

by barryyip0625
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_list_members

Lists members of a specified Discord server along with their roles. Supports pagination via user ID and limit.

Instructions

Lists members in a Discord server with their roles

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": {
      "guildId": "<guildId>"
    },
    "name": "discord_list_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoUser ID to paginate after
limitNoMaximum number of members to return (default 100, max 1000)
guildIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It notes only that members are listed and does not disclose pagination behavior, rate-limit implications, member-intent requirements, or that results may be incomplete without specific permissions.

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?

One clear, compact sentence with no redundancy or extraneous information.

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?

The description is enough for basic invocation but lacks context about return shape, pagination loop, or permissions. Since no output schema exists, the description could have explained what the result contains beyond 'members with roles'.

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 provides descriptions for after and limit; guildId has no description but the main description clarifies it is the Discord server. The description adds little beyond the schema, so a middle score is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states a specific action (lists members), resource (Discord server), and includes roles in output. It is distinct from sibling tools like discord_get_member and discord_list_roles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 instead of alternatives such as discord_get_member for single members or discord_list_roles for roles, nor any context about pagination or large servers.

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

Deploy Server

Other Tools