discord-mcp

members_list_bans

Read-onlyIdempotent

List banned members in a guild with pagination and ban reasons, so moderators can audit history or export the ban list.

Instructions

Purpose: List bans in a guild (paginated).

When to use:

Audit moderation history; export ban list.

Pagination: before/after are user-id cursors. limit 1-1000.

Returns: {bans:[{user_id, username, reason}], count}.

Input Schema

TableJSON Schema

Name	Required	Description
`after`	No	Pagination cursor: bans with user-id > this
`limit`	No	Max bans per page (1-1000, default 1000)
`before`	No	Pagination cursor: bans with user-id < this
`guild_id`	Yes	Guild to list bans for

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.28.0Sep 15, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "bans": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "reason": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "user_id": {
-              "description": "Discord user ID",
-              "pattern": "^\\d{17,20}$",
-              "type": "string"
-            },
-            "username": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "user_id",
-            "username",
-            "reason"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "count": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "bans",
-      "count"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "bans": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "reason": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "user_id": {
+              "description": "Discord user ID",
+              "pattern": "^\\d{17,20}$",
+              "type": "string"
+            },
+            "username": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "user_id",
+            "username",
+            "reason"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "count": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "bans",
+      "count"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The annotations already indicate readOnly, openWorld, and idempotent behavior, which the description does not contradict. The description adds valuable behavioral context beyond annotations, such as the exact return format ({bans:[...], count}) and pagination cursor semantics (user-id based). This is transparent about what the tool returns and how it behaves.

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?

The description is well-structured with clear sections: Purpose, When to use, Pagination, and Returns. It is concise, with no redundant sentences, and the most critical information (purpose) is front-loaded. Every sentence serves a distinct informational purpose.

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

Completeness5/5

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

Given the tool's moderate complexity, the description covers all essential aspects: purpose, usage context, pagination behavior, and return format. Since an output schema is present, the description doesn't need to explain return values further. The annotations cover safety properties, and the description fills the remaining gaps, making it complete for an agent to invoke correctly.

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

Parameters4/5

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

The input schema already has 100% description coverage for all parameters, so the baseline is 3. The description adds a concise summary of pagination (before/after are user-id cursors, limit 1-1000) that reinforces the schema details. It doesn't add substantial new semantics, but the reinforcement is mildly helpful, justifying a slight increase to 4.

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?

The description clearly states the tool lists bans in a guild with pagination. It identifies the specific resource (bans) and the context (guild), and distinguishes itself from related tools like members_get_ban by focusing on listing all bans. It also specifies the output structure, making it unambiguous.

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?

The 'When to use' section provides clear use cases: auditing moderation history and exporting ban lists. It does not explicitly state when not to use this tool or mention alternatives like members_get_ban for a single ban, but the use cases are sufficient for typical selection scenarios.

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

Deploy Server