Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

ban_member

Destructive

Bans a user from a Discord server and optionally deletes their recent messages to enforce moderation.

Instructions

Ban a user from a server, optionally deleting their recent messages. [PUT /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": "ban_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
user_idYesUser ID
guild_idYesServer (guild) ID
delete_message_secondsNoAlso delete their messages from the last N seconds (0-604800)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the danger profile is covered structurally. The description adds useful behavioral detail — that message purging is optional and tied to a time window — but says nothing about irreversibility, required permissions, or what happens on a repeat ban.

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?

One sentence plus the endpoint reference, with the core action front-loaded and the optional modifier attached immediately. There is no filler wording to trim.

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?

For a destructive four-parameter mutation with no output schema, the definition covers the action and the optional side effect but omits permission requirements, failure modes (unknown user, missing guild), and confirmation that success returns no body. Adequate, but thin given the tool's risk.

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%, so all four parameters are already documented, including the 0-604800 range on delete_message_seconds. The description only restates the optional message-deletion concept and adds no syntax or interaction detail beyond the schema, making the baseline 3 appropriate.

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 gives a specific verb and resource ('Ban a user from a server') plus the optional message-deletion behavior and the underlying PUT endpoint. It is clearly distinguishable from bulk_ban_members by the singular 'a user', but it never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the single-user ban action, but there is no statement of when to prefer it over kick_member, bulk_ban_members, or timeout_member, and no preconditions such as requiring the target to be a member or the bot to hold ban permissions.

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