MCP Discord Bot Server

discord_list_members

Fetch a Discord guild's member list by guild ID, with an optional result limit, for moderation, analytics, or outreach.

Instructions

List members of a Discord guild (server).

Args:
    guild_id: The ID of the Discord guild.
    limit: Maximum number of members to return (default: 100).

Returns:
    JSON array of member objects.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of members to return. Default is 100.
`guild_id`	Yes	The ID of the Discord guild (server) to list members for. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it is silent on how the member list is paginated, whether limit caps at some server-side maximum, whether results are ordered, and whether special permissions are needed. The only behavioral note is the return type, which the output schema already covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in a single sentence, and the Args/Returns blocks are short. The Args section is largely redundant with the schema, which slightly blunts the value of the otherwise efficient structure.

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 tool has an output schema, so return values need not be explained, and the two parameters are fully documented in the schema. However, with no annotations at all, the definition leaves permissions and pagination behavior entirely unaddressed, which an agent would benefit from knowing.

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 schema already documents both guild_id and limit, including the default of 100. The description's Args section merely restates that information without adding format, range, or edge-case detail. Baseline 3 applies.

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 opening sentence states a specific verb and resource: 'List members of a Discord guild (server).' That cleanly separates it from siblings like discord_list_guilds and discord_list_channels, which return different entity types. It does not, however, explicitly contrast itself with any sibling.

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?

There is no statement of when to use this tool versus alternatives, no prerequisites (e.g., bot permissions/privileged intents required to enumerate members), and no mention of when another tool would be preferable. Usage is only inferable from the name.

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

Deploy Server