members_modify
Modify a guild member’s nick, roles, voice state, or timeout. One tool covers the full PATCH /guilds/{guild.id}/members/{user.id} surface.
When to use
Section titled “When to use”- Set/clear nickname (
nick). - Replace role set wholesale (
roles). To add/remove a single role, prefermembers_add_role/members_remove_role. - Server mute/deaf in voice (
mute,deaf). - Move user between voice channels (
channel_id). - Apply a timeout (
communication_disabled_until, ISO-8601 timestamp). - Adjust member flags bitfield (
flags).
Pass only the fields you want to change. Discord ignores undefined fields.
MCP call example
Section titled “MCP call example”{ "name": "members_modify", "arguments": { "guild_id": "123456789012345678", "user_id": "123456789012345678", "nick": "example" }}| 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 modify |
nick |
string | null | no | Nickname (null to clear) | |
roles |
array<string> | no | Replace role set wholesale | |
mute |
boolean | no | Server-mute in voice | |
deaf |
boolean | no | Server-deafen in voice | |
channel_id |
string | null | no | Voice channel to move to (null to disconnect) | |
communication_disabled_until |
string | null | no | ISO-8601 timestamp ending the timeout (null to clear, max 28 days from now) | |
flags |
integer | no | Member flags bitfield | |
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 modify" }, "nick": { "description": "Nickname (null to clear)", "anyOf": [ { "type": "string", "maxLength": 32 }, { "type": "null" } ] }, "roles": { "description": "Replace role set wholesale", "type": "array", "items": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord role ID" } }, "mute": { "description": "Server-mute in voice", "type": "boolean" }, "deaf": { "description": "Server-deafen in voice", "type": "boolean" }, "channel_id": { "description": "Voice channel to move to (null to disconnect)", "anyOf": [ { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord channel ID (snowflake)" }, { "type": "null" } ] }, "communication_disabled_until": { "description": "ISO-8601 timestamp ending the timeout (null to clear, max 28 days from now)", "type": [ "string", "null" ] }, "flags": { "description": "Member flags bitfield", "type": "integer" }, "audit_reason": { "description": "Reason recorded in audit log (X-Audit-Log-Reason header)", "type": "string", "minLength": 1, "maxLength": 512 } }, "required": [ "guild_id", "user_id" ]}Returns
Section titled “Returns”{user_id, nick, roles}.
Example structured result
Section titled “Example structured result”{ "user_id": "123456789012345678", "nick": "example", "roles": [ "123456789012345678" ]}Output schema
Section titled “Output schema”| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
user_id |
string | yes | pattern: ^\d{17,20}$ |
Discord user ID |
nick |
string | null | yes | ||
roles |
array<string> | yes |
Complete output JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "user_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord user ID" }, "nick": { "type": [ "string", "null" ] }, "roles": { "type": "array", "items": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord role ID" } } }, "required": [ "user_id", "nick", "roles" ], "additionalProperties": false}Annotations
Section titled “Annotations”| Property | Value |
|---|---|
| Read-only | no |
| Destructive | no |
| Idempotent | yes |
| Open-world | yes |
| Confirmation required | no |
Access and common errors
Section titled “Access and common errors”- The
memberscategory must be enabled byMCP_CATEGORIESwhen an allowlist is set. - Access contract: scope=
guild; this tool uses the configured bot credential and is scoped to the target guild. - No named Discord permission bit is asserted by this contract. Conditional access is selected from payload fields:
nick→MANAGE_NICKNAMES;roles→MANAGE_ROLES;mute→MUTE_MEMBERS;deaf→DEAFEN_MEMBERS;channel_id→MOVE_MEMBERS;channel_id(non-null) →MOVE_MEMBERS,CONNECT;communication_disabled_until→MODERATE_MEMBERS. An unrecognized action payload remains unresolved. Permission evidence is taken from target field(s):channel_id. - Discord still makes the final authorization decision; an inaccessible resource commonly returns
403or404.
Trust boundary
Section titled “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
Section titled “Source”packages/mcp-core/src/tools/members/modify.ts

