Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_list_members

List or search members of a Discord server; use query or after paging to navigate large servers.

Instructions

List or search members of a server. Large servers need query or after paging.

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
afterNoReturn members after this user id
limitNo
queryNoMatch username or nickname
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the paging constraint for large servers, which is real behavioral context. It omits permission/intent requirements (guild member access), rate-limit behavior, and what the response contains, leaving gaps for a read tool with no annotation coverage.

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?

Two short sentences with zero filler, and the most important constraint (large-server paging) is front-loaded in the second sentence. Nothing can be trimmed without losing 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?

No output schema exists, so the description should hint at what is returned (member objects, pagination cursor), and it does not. For a four-parameter list tool with no annotations, it is minimal but functional.

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 coverage is 75%, so most parameters are already documented. The description adds meaning to 'after' as a paging mechanism rather than a time filter, which is useful clarification, but says nothing about limit defaults or how query matching behaves against both username and nickname.

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?

States a specific verb set (list or search) and resource (members of a server), which is clear enough to distinguish from role-scoped or ban-list siblings. It stops short of naming a sibling it is not, so differentiation relies on the agent's reading of the sibling names.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives one concrete usage rule – large servers require query or after-based paging – which is genuinely actionable. It offers no guidance on alternatives such as discord_list_role_members or discord_list_bans, leaving selection between member-listing variants implicit.

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