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

List bans

list_bans
Read-only

Retrieve the current bans in a Discord server with reasons, using paging to review moderation status. Use it to audit who is banned and why, one page at a time.

Instructions

Current bans with reasons, paged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bans"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoUser ID cursor for paging.
guildNoGuild (server) name or ID. Omit to use the default guild.
limitNoMax entries. Default 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint already declares this is a safe read, so the description only needs to add context beyond that. It does contribute the facts that only active bans are returned and that results are paginated, but it omits ordering, whether expired bans appear, and how paging terminates — gaps that matter since there is no output schema.

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?

Six words with no filler and the key qualifier ('current') front-loaded. It is telegraphic to the point of being clipped, but nothing is wasted.

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, fully-annotated, fully-documented read tool this is nearly adequate, but with no output schema the description should say more about the returned record shape than just 'with reasons' (e.g. user, moderator, timestamp).

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 three parameters (after, guild, limit) are already documented with defaults and bounds. The description's only addition is the word 'paged', which hints at cursor usage without explaining it; baseline 3 applies.

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 names the resource (bans) and narrows it to current bans, plus what comes back (reasons) and that it is paged. That is enough to distinguish it from mutation siblings like ban_member and bulk_ban, though it is a noun phrase with no explicit verb.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of prerequisites (e.g. moderation permissions), and no mention of alternatives. A reader can infer this is the read path for bans, but nothing is stated explicitly.

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