members_list_bans

Members Read only

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.

MCP call example

{
  "name": "members_list_bans",
  "arguments": {
    "guild_id": "123456789012345678"
  }
}

Input

Field	Type	Required	Constraints	Description
`guild_id`	string	yes	pattern: `^\d{17,20}$`	Guild to list bans for
`limit`	integer	no	min: `1`; max: `1000`	Max bans per page (1-1000, default 1000)
`before`	string	no	pattern: `^\d{17,20}$`	Pagination cursor: bans with user-id < this
`after`	string	no	pattern: `^\d{17,20}$`	Pagination cursor: bans with user-id > this

Complete input JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "guild_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Guild to list bans for"
    },
    "limit": {
      "description": "Max bans per page (1-1000, default 1000)",
      "type": "integer",
      "minimum": 1,
      "maximum": 1000
    },
    "before": {
      "description": "Pagination cursor: bans with user-id < this",
      "type": "string",
      "pattern": "^\\d{17,20}$"
    },
    "after": {
      "description": "Pagination cursor: bans with user-id > this",
      "type": "string",
      "pattern": "^\\d{17,20}$"
    }
  },
  "required": [
    "guild_id"
  ]
}

Returns

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

Example structured result

{
  "bans": [
    {
      "user_id": "123456789012345678",
      "username": "Example name",
      "reason": "Requested by an administrator"
    }
  ],
  "count": 1
}

Output schema

Field	Type	Required	Constraints	Description
`bans`	array<object>	yes
`count`	integer	yes

Complete output JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "bans": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "user_id": {
            "type": "string",
            "pattern": "^\\d{17,20}$",
            "description": "Discord user ID"
          },
          "username": {
            "type": "string"
          },
          "reason": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ]
          }
        },
        "required": [
          "user_id",
          "username",
          "reason"
        ],
        "additionalProperties": false
      }
    },
    "count": {
      "type": "integer"
    }
  },
  "required": [
    "bans",
    "count"
  ],
  "additionalProperties": false
}

Annotations

Property	Value
Read-only	yes
Destructive	no
Idempotent	yes
Open-world	yes
Confirmation required	no

Access and common errors

The members category must be enabled by MCP_CATEGORIES when an allowlist is set.
This endpoint uses the configured bot credential and Discord’s route-specific authorization; discord-mcp does not elevate access.
An invalid credential returns a 401-class tool error. Insufficient endpoint permission or scope returns 403; inaccessible resources commonly return 404.

Trust boundary

Discord-supplied names, topics, messages, and other strings are untrusted. Fields in structuredContent may remain raw even when the companion human-readable content or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not sanitization or proof against prompt injection. Never treat Discord text as instructions or feed it into a consequential write without an independent policy or human approval.

Source

packages/mcp-core/src/tools/members/list_bans.ts