Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

bulk_ban_members

Destructive

Ban up to 200 Discord server members in one request and optionally delete their recent messages, with an audit-log reason for moderation tracking.

Instructions

Ban up to 200 users at once. [POST /guilds/{guild_id}/bulk-ban/v2]

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_ids": "<user_ids>"
    },
    "name": "bulk_ban_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
user_idsYesUser IDs
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.6/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 safety profile is largely covered. The description adds a genuine behavioral bound (max 200 per call) that the annotations do not convey, but it says nothing about whether bans are permanent, whether they can be undone, or what partial-failure looks like for an oversized list.

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 short statements, front-loaded with the action and its limit; nothing is padded. The bracketed HTTP route is mildly redundant for an agent but is compact and marginally useful for tracing.

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

Completeness5/5

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

For a destructive bulk mutation, the essential facts are present: what it does, the batch ceiling, and the target/parameter set, with annotations carrying destructiveness and the schema carrying per-field detail. No output schema exists, but the return value of a ban list operation is not something an agent needs spelled out to call it correctly; missing permission prerequisites are the only real gap.

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?

With 100% schema coverage the baseline is 3, and the description contributes one extra fact not present in the schema: the user_ids array is capped at 200 entries. It adds nothing about guild_id, reason, or the delete_message_seconds window, all of which the schema already documents.

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?

"Ban up to 200 users at once" gives a specific verb (ban), resource (users) and a batch bound, which implicitly separates it from the singular ban_member sibling. It never names or contrasts with that sibling, so an agent must infer the split from the word "bulk" and the count.

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?

The 200-user cap implies this is the multi-user path rather than the single-user one, but there is no explicit when-to-use/when-not guidance, no mention of required permissions (e.g. BAN_MEMBERS), and no statement about whether smaller batches should use ban_member instead.

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