Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_list_bans

Read-only

List banned users in a Discord server with their ban reasons. Paginate through up to 1000 bans per page using a cursor; requires Ban Members permission.

Instructions

List the users banned from the server, with their ban reasons. Returns { bans: [...], nextCursor }. A page holds up to 1000 bans; if nextCursor is non-null, pass it back as after to fetch the next page. Requires the Ban Members permission. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor: a user ID (snowflake). Pass the previous response's nextCursor to fetch the next page.
limitNoMax bans per page (1–1000). Default 1000.
guild_idYesDiscord server (guild) ID (snowflake).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bansYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed7 schema fields changedv2.0.0
    • addedInput schema / properties / after / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / guild_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / limit / default
      Added value: +1000
    • addedInput schema / properties / limit / maximum
      Added value: +1000
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "bans": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "reason": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "user_id": {
+            "type": "string"
+          },
+          "username": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "user_id",
+          "username",
+          "reason"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextCursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "bans",
+    "nextCursor"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changedv1.7.0
    • addedInput schema / properties / after
      Added value: +{
+  "description": "Pagination cursor: a user ID (snowflake). Pass the previous response's nextCursor to fetch the next page.",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Optional max number of bans to fetch. Omit to fetch all."New value: +"Max bans per page (1–1000). Default 1000."
  4. Changed2 schema fields changedv1.6.0
    • addedInput schema / properties / guild_id / description
      Added value: +"Discord server (guild) ID (snowflake)."
    • changedInput schema / properties / limit / description
      Previous value: -"Max bans to fetch."New value: +"Optional max number of bans to fetch. Omit to fetch all."
  5. Addedv1.5.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description adds valuable behavioral detail: pagination behavior (1000 per page, nextCursor as `after`), the returned shape, required permission, and an explicit read-only statement. This fully informs the agent of what to expect.

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?

Three tight sentences: the main purpose, the pagination contract, and the permission/safety note. No filler; every sentence earns its place and the key information is front-loaded.

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?

For a paginated list tool, the description is complete: it covers purpose, return shape, pagination mechanics, permission requirement, and read-only nature. Even though an output schema exists, the description provides the essential runtime context an agent needs to invoke and navigate the tool 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?

Schema coverage is 100%, so parameters are already documented. The description adds value by explaining the pagination flow between `nextCursor` and `after`, and connecting the 1000-bans page limit to the `limit` parameter, going beyond the schema's individual field descriptions.

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 states a specific verb ('List') and resource ('users banned from the server'), and clarifies it includes ban reasons. This clearly differentiates it from sibling tools like discord_list_members or discord_ban_member.

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

Usage Guidelines3/5

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

The description implies usage for retrieving banned users and notes the required Ban Members permission, but it does not explicitly state when to prefer this over alternatives or when not to use it. Usage context is reasonable but left to inference.

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