Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_bans

Read-only

Retrieve banned users from a Discord server by guild ID, with optional pagination using before, after, and limit parameters.

Instructions

List banned users. [GET /guilds/{guild_id}/bans]

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

Input Schema

NameRequiredDescriptionDefault
afterNoReturn items after this ID (pagination)
limitNoMax results
beforeNoReturn items before this ID (pagination)
guild_idYesServer (guild) ID

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the REST endpoint reference, which is mild extra context, but says nothing about the BAN_MEMBERS permission requirement, pagination behavior, or result shape.

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 fragments with the purpose front-loaded and zero filler. The bracketed endpoint notation is somewhat terse but earns its place as API context for an agent that reasons in REST terms.

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?

A simple read-only list tool with full schema coverage and annotations is adequately served, but the absence of permission requirements and any routing hint versus search_guild_bans leaves real gaps. With no output schema, the description could also say more about what a ban record contains.

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 guild_id, limit, after and before are all documented in the schema itself. The description adds no additional meaning about pagination semantics or default limits, so the baseline of 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?

States a specific verb+resource ("List banned users") that an agent can immediately map to guild ban retrieval. However, it does not distinguish itself from the sibling search_guild_bans, which reads as a near-identical operation, so sibling differentiation is missing.

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?

The description gives no when-to-use or when-not-to-use guidance and never mentions search_guild_bans as an alternative for filtered lookup. An agent choosing between listing all bans and searching bans gets no help from this text.

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