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

discord-admin-mcp

by pedroaop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_bans

Retrieve the list of banned users for a Discord server using its guild ID. Use this to review or audit bans.

Instructions

Lista usuários banidos.

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_bans"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses only that records are listed. It says nothing about required permissions, whether results are paginated or capped, whether the guild must be one the caller administers, or how bans are ordered.

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 short, front-loaded sentence with no filler. It is efficient, though the brevity stems partly from under-specification rather than deliberate economy.

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?

An output schema exists, so return values need not be described, but for a guild-scoped administrative read with zero annotation coverage the definition leaves the agent without the permission, scoping, and result-size context it needs to invoke the tool confidently.

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 description coverage is 0% for the single required guild_id parameter, and the description never mentions it. It neither confirms that the scope is a guild nor clarifies the expected ID format, so the schema gap is not compensated.

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 gives a specific verb and resource ("Lista usuários banidos" = lists banned users), which is distinguishable from the mutation siblings ban_member and unban_member. It does not, however, contrast itself with adjacent read tools such as list_members or search_members, and it is written in a different language than the surrounding tool set.

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 guidance on when to call this versus ban_member/unban_member/search_members, and no mention of prerequisites such as needing a guild context or ban-list permissions. An agent must infer usage entirely from the name.

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