discord_members
List members of a Discord guild using a bot token and guild ID.
Instructions
List members of a Discord guild.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| bot_token | Yes | ||
| guild_id | Yes | ||
| limit | No |
List members of a Discord guild using a bot token and guild ID.
List members of a Discord guild.
| Name | Required | Description | Default |
|---|---|---|---|
| bot_token | Yes | ||
| guild_id | Yes | ||
| limit | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Lacks disclosure of behavioral traits such as required intents or permissions, pagination behavior, or output format. With no annotations, description should provide more context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise but at the cost of completeness. Lacks parameter details and usage context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Incomplete for a tool with no output schema and no annotation disclosures. Missing details on authentication (bot_token purpose), limit parameter, and return format.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameter explanations in description, and schema has no parameter descriptions. Description does not clarify the meaning or usage of bot_token, guild_id, or limit.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clear verb 'List' targeting 'members of a Discord guild', distinct from sibling Discord tools like discord_channels or discord_send.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance provided. Does not specify when to use this tool over sibling Discord tools or mention any prerequisites like bot permissions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'
If you have feedback or need assistance with the MCP directory API, please join our Discord server