Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_members

Read-only

Retrieve a Discord server's member list by guild ID, with pagination and result limits. Use it to inspect members; for targeted searches, use search_members instead.

Instructions

List server members (bots; user accounts usually need Manage Server). For search use search_members. [GET /guilds/{guild_id}/members]

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": {
      "guild_id": "<guild_id>"
    },
    "name": "list_guild_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoReturn items after this ID (pagination)
limitNoMax results
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, open-world operation. The description adds meaningful behavioral context beyond that by noting the permission requirement for user accounts and identifying the underlying endpoint.

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 definition is short, front-loaded, and free of redundant wording. The alternative tool and permission caveat are included without bloating the description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter list tool with full schema coverage and useful annotations, the description covers purpose, the search alternative, permission context, and the endpoint. It does not describe pagination behavior or return shape, but those are minor gaps here.

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 input schema already documents guild_id, after, and limit. The description adds no parameter-level detail beyond the schema, so the baseline of 3 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?

The description states a specific verb and resource: "List server members." It also explicitly distinguishes itself from the search-oriented sibling by saying "For search use search_members."

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

Usage Guidelines4/5

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

It gives a clear routing rule: use this tool for listing, and use search_members for searching. It also notes that user accounts usually need Manage Server, which is useful usage context, though it does not state other exclusions or pagination expectations.

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