Skip to main content
Glama
berkal749

mcp-discord-mod

by berkal749

discord_mod_unban_member

Unban a user from a Discord server using the server ID and user ID, optionally providing a reason.

Instructions

Unban a user from a Discord server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoReason for the unban
userIdYesThe ID of the user to unban
guildIdYesThe ID of the server
Behavior2/5

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

With no annotations provided, the short description 'Unban a user' carries the full burden of behavioral disclosure. It fails to mention required permissions, side effects (e.g., immediate effect, audit log entry), or idempotency, leaving significant behavioral uncertainty for a mutation tool.

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 description is a single concise sentence front-loading the core action. Every word is functional, but it could be slightly too brief, missing context without being verbose.

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

Completeness2/5

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

Given no output schema and no annotations, the description should provide more context about return values, error states, or preconditions. It only states the action, leaving agents without sufficient information for correct 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% with each parameter (reason, userId, guildId) described in the schema. The description adds no further parameter details beyond the purpose, so baseline 3 is appropriate.

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?

The description explicitly states 'Unban a user from a Discord server,' clearly identifying the verb (unban) and resource (user). This action is distinct from siblings like discord_mod_ban_member (ban) and other moderation tools, leaving no ambiguity about its purpose.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., when a user is banned, requirements like user must be banned first). The description lacks context about appropriate scenarios or exclusions, limiting the agent's ability to choose correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/berkal749/mcp-discord-mod'

If you have feedback or need assistance with the MCP directory API, please join our Discord server