Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Bulk ban

bulk_ban
Destructive

Ban up to 200 users by ID at once for raid cleanup, previewing the action before confirmation and reporting which bans succeeded or failed.

Instructions

Ban up to 200 users at once by ID, for raid cleanup. Safe to call directly: the first call changes nothing and returns a preview plus a confirm_token; repeating the call with the token performs the bans. Reports which bans succeeded and which failed.

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": {
      "user_ids": "<user_ids>"
    },
    "name": "bulk_ban"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoGuild (server) name or ID. Omit to use the default guild.
reasonNo
dry_runNo
user_idsYesUser IDs to ban.
confirm_tokenNoThe token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.
delete_message_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token / description
      Added value: +"The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree."
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true; the description adds the genuinely non-obvious safety contract that the first call mutates nothing and returns a preview plus confirm_token, that the token is what triggers execution, and that per-user success/failure is reported. That is substantial behavioral value beyond the annotations, and it does not contradict them since the eventual ban is indeed destructive.

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?

Three tight sentences with no filler: purpose and scale first, then the safety/confirmation mechanic, then the result shape. Each sentence carries distinct information an agent needs.

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

Completeness4/5

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

With no output schema, the description correctly compensates by describing the return value (per-user success/failure) and the preview payload. It is close to complete for a destructive bulk tool, but the unexplained dry_run parameter sits awkwardly beside the described preview-first behavior and could confuse an agent about which mechanism to use.

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?

At 50% schema coverage, the description covers the two most important parameters, clarifying user_ids (ID-based, with the 200 cap) and the confirm_token flow. The other four parameters (guild, reason, dry_run, delete_message_seconds) get no mention, and dry_run's relationship to the preview behavior is left ambiguous.

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?

States a specific verb (ban), resource (users), mechanism (by ID), scale limit (up to 200 at once), and use case (raid cleanup). The 'at once'/'bulk' framing makes it distinguishable from ban_member without opening either schema.

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

Usage Guidelines4/5

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

Gives a clear usage context ('for raid cleanup') and spells out the intended two-call workflow: call once for a preview, then repeat with the confirm_token to execute. It does not explicitly say when to prefer ban_member or other single-target tools instead, so it stops short of full when-not guidance.

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