Skip to main content
Glama
Sign In
Guildora

Guildora

by az-xx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List or search members

list_members
Read-onlyIdempotent

Lists Discord server members with IDs, roles, and join dates; search username or nickname prefixes or filter by role to page through and find members.

Instructions

Lists server members with IDs, roles and join date. With "query", searches usernames and nicknames that start with the text (no special intent needed). Without a query it pages through all members, which needs the Server Members intent. "role" keeps only members with that role. Use get_member for one member.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoOnly members with this role (ID, mention or name).
guildNoServer ID or name. Optional if DISCORD_GUILD_ID is set or the bot is in one server.
limitNoMax items to return (1-100, default 50).
queryNoUsername or nickname prefix to search for.
cursorNoThe next_cursor value from a previous call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses a genuine operational gotcha: full listing requires the privileged Server Members intent while query-mode does not. It also explains that results are paged, which pairs with the cursor parameter and is not stated in the annotations.

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?

Four compact sentences, each carrying distinct information: return fields, query behavior, non-query behavior plus intent requirement, role filter, and the sibling pointer. Nothing is repeated and the core behavior is front-loaded.

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

Completeness5/5

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

With no output schema, the description compensates by naming the returned fields, and it covers the privileged-intent prerequisite and pagination model. For a 5-parameter, zero-required read tool, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that the presence or absence of 'query' switches the tool between search mode and full pagination, and that the match is prefix-based on username or nickname. The 'cursor' parameter is left to the schema, which is acceptable given full coverage.

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?

States a specific verb and resource ('Lists server members') plus the returned fields (IDs, roles, join date), and explicitly names the single-member alternative get_member. An agent can distinguish this from get_member without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit mode selection: with 'query' it is a prefix search needing no special intent; without 'query' it pages through all members and requires the Server Members intent. It also documents the 'role' filter and points to get_member for a single member, covering when-to-use and alternatives.

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