Skip to main content
Glama
Sign In
better-discord-mcp

better-discord-mcp

by Sys0xdbg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

discord_bulk_ban

Ban up to 200 Discord users at once, with optional reason and message deletion. Requires Ban Members and Manage Guild permissions.

Instructions

Ban many users at once (up to 200). Requires Ban Members + Manage Guild.

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": {
      "guildId": "<guildId>",
      "userIds": "<userIds>"
    },
    "name": "discord_bulk_ban"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
confirmNoSet true to actually perform this destructive action
guildIdYes
userIdsYes
deleteMessageSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations; description says nothing about destructive nature or that confirm must be true to execute. The confirm parameter's schema description covers destructiveness, but the tool description itself lacks this critical behavioral detail.

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?

One clear sentence, no wasted words. Could benefit from adding key behavioral notes without being bulky.

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?

For a destructive batch tool with 5 parameters, no output schema, and no annotations, the description is too minimal. Missing confirm gate, parameter explanations, and return behavior.

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 coverage is low (20%). Description adds no value for any of the 5 parameters. Does not explain guildId, userIds, reason, or deleteMessageSeconds.

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?

Clearly states it bans many users at once (up to 200), a specific verb+resource+capacity. Distinguishes from sibling discord_ban_user which is for single bans.

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?

Mentions required permissions (Ban Members + Manage Guild) and implies batch usage. However, does not explicitly compare with single-ban tool or state when not to use.

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