discord-mcp

Bans (admin)

discord_admin_bans

Read-only

List banned users with their reasons or check if a specific user is banned. Use it to audit server bans and verify user status.

Instructions

List banned users with reasons, or check whether one user is banned. (Ban and unban with discord_admin_moderate_member.)

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": "discord_admin_bans"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`user_id`	No	Check this user only

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results carry ban reasons and that mutations live in a different tool, but says nothing about likely rate limits, permission requirements, or how large lists are returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the read behavior and closing with the sibling pointer. No redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only tool with annotations and no output schema, this covers the essential usage split and the write-path handoff. Remaining gaps (pagination of long ban lists, what fields come back besides reason) are minor given the tool's simplicity.

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 coverage is 50%: user_id is described in the schema ('Check this user only') and the description reinforces that single-user mode. The limit parameter carries only machine constraints (default 100, max 1000) and is never mentioned in prose, so the description adds little beyond the schema.

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?

States specific verbs and the resource: listing banned users (with reasons) or checking a single user's ban status. It also names the sibling tool that handles the mutation side, so an agent can distinguish read from write without opening schemas.

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?

Explicitly routes ban/unban actions to discord_admin_moderate_member, and the 'check whether one user is banned' phrasing (paired with the schema's user_id) implies the filter-vs-list distinction. It stops short of stating anything about paging through large ban lists when user_id is omitted.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server