Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

unban_member

Destructive

Removes a Discord server ban for a specified user ID within a guild, optionally recording a reason in the audit log, restoring server access.

Instructions

Unban a user. [DELETE /guilds/{guild_id}/bans/{user_id}]

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>",
      "user_id": "<user_id>"
    },
    "name": "unban_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
user_idYesUser ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the mutation/risk profile is fully covered by structured data. The description adds only the raw REST endpoint mapping, which restates the operation rather than adding context such as permission requirements, idempotency, or whether the audit-log reason is recorded when omitted.

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?

Two fragments, front-loaded with the action and followed by the endpoint reference; there is no filler or redundancy. It is efficient, though the brevity comes at the cost of substance captured in other dimensions.

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?

This is a simple three-parameter mutation with a fully described schema and safety annotations, so the definition is minimally sufficient. It still omits permission prerequisites and failure behavior, which matter for a destructive moderation action.

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 description coverage is 100% – guild_id, user_id and reason are each documented in the schema, including that reason appears in the audit log. The description contributes nothing about the parameters, so the baseline of 3 applies since the schema does all the work.

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?

The description states a specific verb and resource ('Unban a user'), which unambiguously identifies the inverse of the sibling ban_member. It does not explicitly name a sibling or scope the operation further, but the action is clear enough that no agent would confuse it with the other member-management tools.

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?

There is no when-to-use guidance, no prerequisite (e.g. the user must currently be banned, caller needs ban permission), and no mention of what to do if the user is not banned. Usage is only implied by the verb itself.

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