Skip to main content
Glama

discord_unban_member

Remove a user's ban from a Discord server by providing guild and user IDs, enabling moderation actions to restore access.

Instructions

Unban a user from a guild.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guild_idYes
user_idYes
reasonNo

Implementation Reference

  • Handler implementation for "discord_unban_member" which unbans a member from a Discord guild.
    case "discord_unban_member": {
      const guild = await discord.guilds.fetch(validateId(args.guild_id, "guild_id"));
      await guild.members.unban(args.user_id as string, args.reason as string | undefined);
      return { content: [{ type: "text", text: `✅ User ${args.user_id} has been unbanned.` }] };
    }
  • Schema definition for "discord_unban_member" tool.
    {
      name: "discord_unban_member",
      description: "Unban a user from a guild.",
      inputSchema: {
        type: "object",
        properties: {
          guild_id: { type: "string" },
          user_id: { type: "string" },
          reason: { type: "string" },
        },
        required: ["guild_id", "user_id"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('Unban') but does not disclose behavioral traits like required permissions (e.g., 'Ban Members'), rate limits, whether it's reversible, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence with zero waste, front-loading the core action. It is appropriately sized for the tool's purpose without unnecessary elaboration.

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 the tool's complexity (a mutation with 3 parameters), lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It does not compensate for missing behavioral details, parameter explanations, or usage context, making it insufficient for safe and effective use.

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

Parameters1/5

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

Schema description coverage is 0%, meaning parameters are undocumented in the schema. The description adds no meaning beyond the tool name, failing to explain what 'guild_id', 'user_id', or 'reason' represent or their expected formats, leaving all three parameters semantically unclear.

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 clearly states the action ('Unban') and the resource ('a user from a guild'), which is specific and unambiguous. However, it does not explicitly differentiate from sibling tools like 'discord_ban_member' or 'discord_kick_member', which would require mentioning it reverses bans specifically.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'discord_ban_member' for banning or 'discord_kick_member' for removal without a ban. It lacks context on prerequisites (e.g., the user must be banned first) or exclusions.

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/PaSympa/discord-mcp'

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