members_remove_role

Members Writes to Discord

Remove a single role from a guild member.

When to use

Targeted role revocation (e.g. revoke @verified).

When not to use

Replacing the entire role set → use members_modify with roles.

MCP call example

{
  "name": "members_remove_role",
  "arguments": {
    "guild_id": "123456789012345678",
    "user_id": "123456789012345678",
    "role_id": "123456789012345678"
  }
}

Input

Field	Type	Required	Constraints	Description
`guild_id`	string	yes	pattern: `^\d{17,20}$`	Guild containing the member
`user_id`	string	yes	pattern: `^\d{17,20}$`	Member to revoke the role from
`role_id`	string	yes	pattern: `^\d{17,20}$`	Role to remove
`audit_reason`	string	no	min length: `1`; max length: `512`	Reason recorded in audit log (X-Audit-Log-Reason header)

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 containing the member"
    },
    "user_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Member to revoke the role from"
    },
    "role_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Role to remove"
    },
    "audit_reason": {
      "description": "Reason recorded in audit log (X-Audit-Log-Reason header)",
      "type": "string",
      "minLength": 1,
      "maxLength": 512
    }
  },
  "required": [
    "guild_id",
    "user_id",
    "role_id"
  ]
}

Returns

{removed, user_id, role_id}. Idempotent - removing a role the user does not have is a no-op.

Example structured result

{
  "removed": true,
  "user_id": "123456789012345678",
  "role_id": "123456789012345678"
}

Output schema

Field	Type	Required	Constraints	Description
`removed`	true	yes
`user_id`	string	yes	pattern: `^\d{17,20}$`	Discord user ID
`role_id`	string	yes	pattern: `^\d{17,20}$`	Discord role ID

Complete output JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "removed": {
      "type": "boolean",
      "const": true
    },
    "user_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Discord user ID"
    },
    "role_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Discord role ID"
    }
  },
  "required": [
    "removed",
    "user_id",
    "role_id"
  ],
  "additionalProperties": false
}

Annotations

Property	Value
Read-only	no
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/remove_role.ts