unban_member
Unban a user from a Discord server. Requires guild ID, user ID, and optional reason.
Instructions
Unban a user from the server
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| guild_id | Yes | ||
| user_id | Yes | ||
| reason | No | Audit log reason (optional) |
Unban a user from a Discord server. Requires guild ID, user ID, and optional reason.
Unban a user from the server
| Name | Required | Description | Default |
|---|---|---|---|
| guild_id | Yes | ||
| user_id | Yes | ||
| reason | No | Audit log reason (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only states the basic action. Does not disclose side effects, permissions, or audit log behavior (despite a 'reason' parameter).
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?
Single sentence is short but underspecified, lacking necessary details. Not balanced—too brief for effective use.
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?
Given no annotations, no output schema, and low parameter coverage, the description fails to provide sufficient context. Does not explain return values or behavior on success/failure.
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?
Only 33% of parameters have schema descriptions; the description adds no additional meaning to 'guild_id' or 'user_id'. The 'reason' parameter is partially described in schema, but description offers no extra context.
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?
Description uses specific verb 'Unban' and resource 'user', clearly indicating the action. It distinguishes from siblings like 'ban_member' by name but does not explicitly differentiate.
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 guidance on when to use this tool versus alternatives like 'ban_member' or 'kick_member'. Lacks context for prerequisites or conditions.
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/iprashantraj/mcp-discord-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server