Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

search_guild_members

Find Discord server members using advanced filters for roles, join date, join source, and safety signals so moderators can review and manage membership.

Instructions

Advanced member search (Manage Server/moderators): filters by roles, join date, join source, safety signals. [POST /guilds/{guild_id}/members-search]

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": "search_guild_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNosort
afterNoReturn items after this ID (pagination)
limitNoMax results
beforeNoReturn items before this ID (pagination)
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
or_queryNoor query
and_queryNoand query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and destructiveHint=false, and the description adds the permission requirement plus the underlying POST endpoint. There is a mild tension between 'search' and readOnlyHint=false, but since the description never claims the call is read-only and POST-search endpoints are commonly non-idempotent, this is not a hard contradiction. It says nothing about pagination limits or rate limiting beyond what the schema 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?

Front-loaded and compact: capability, audience, filter dimensions, then the endpoint. Every element carries information; 'Advanced' is the only mildly padded word. No redundant restatement of the tool name.

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?

For an 8-parameter tool with nested query objects and no output schema, the description covers purpose, permission scope, and filter categories adequately. It leaves the agent without guidance on the opaque query object structure and on result shape or paging behavior, which are the main risks for incorrect invocation.

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 100%, but several schema descriptions are near-placeholders ('and query', 'or query', 'sort'), so the description's enumeration of filterable dimensions (roles, join date, join source, safety signals) genuinely adds domain meaning. It still does not explain how to structure the nested and_query/or_query objects or how sort interacts with before/after cursors, which is the highest-value missing detail.

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 and resource ('member search') and qualifies it as 'advanced' with named filter dimensions, which distinguishes it from the plain listing siblings such as list_guild_members. It stops short of naming the closest alternatives (search_members, query_guild_members), so the differentiation is implied rather than explicit.

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?

The parenthetical '(Manage Server/moderators)' signals the required permission level and the intended audience, which is useful context for when this tool is callable. However, there is no statement of when to prefer this over the sibling search/query member tools, nor any exclusion or prerequisite guidance.

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