Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_list_bans

Retrieve a Discord server's banned users by guild ID and optional limit to review moderation records. Requires Ban Members permission.

Instructions

List banned users. Requires Ban Members.

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>"
    },
    "name": "discord_list_bans"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the Ban Members permission requirement, which is real context an agent needs before calling. But it says nothing about pagination, how the limit interacts with Discord's server-side cap, or what a ban entry contains, leaving meaningful behavior undisclosed.

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 sentences, front-loaded with purpose and followed by the prerequisite, with no filler. It is efficient, though the extreme terseness is part of why behavioral and parameter detail is absent.

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 simple two-parameter read tool with no output schema and no annotations, the description covers purpose and permission adequately. It is not complete enough regarding the undocumented limit parameter and the shape of returned ban entries, both of which an agent would want before calling.

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

Parameters2/5

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

Schema coverage is only 50%: guildId is documented as a snowflake, but limit has no description in the schema and is never mentioned in the description. The description does not compensate for that gap, so an agent must infer the meaning, ordering, and pagination implications of limit on its own.

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 states a specific verb and resource: 'List banned users.' An agent can immediately tell this retrieves guild bans rather than members or roles. It stops short of distinguishing itself from the near-sibling discord_list_blocked, which an agent could plausibly confuse with bans.

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?

'Requires Ban Members' gives a concrete permission prerequisite, which is genuine usage guidance. However, there is no statement of when to prefer this over discord_list_blocked or discord_list_members, and no note on whether guildId must be the current guild or any guild the bot is in.

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