discord-mcp

members_modify

Idempotent

Update a Discord member's nickname, roles, voice state, timeout, or flags in a single request. Pass only the fields you want to change.

Instructions

Purpose: 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:

Set/clear nickname (nick).
Replace role set wholesale (roles). To add/remove a single role, prefer members_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.

Returns: {user_id, nick, roles}.

Input Schema

TableJSON Schema

Name	Required	Description
`deaf`	No	Server-deafen in voice
`mute`	No	Server-mute in voice
`nick`	No	Nickname (null to clear)
`flags`	No	Member flags bitfield
`roles`	No	Replace role set wholesale
`user_id`	Yes	Member to modify
`guild_id`	Yes	Guild containing the member
`channel_id`	No	Voice channel to move to (null to disconnect)
`audit_reason`	No	Reason recorded in audit log (X-Audit-Log-Reason header)
`communication_disabled_until`	No	ISO-8601 timestamp ending the timeout (null to clear, max 28 days from now)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.28.0Sep 15, 2026

removedInput schema / properties / communication_disabled_until / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / communication_disabled_until / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "nick": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "roles": {
-        "items": {
-          "description": "Discord role ID",
-          "pattern": "^\\d{17,20}$",
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "user_id": {
-        "description": "Discord user ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "user_id",
-      "nick",
-      "roles"
-    ],
-    "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": {
+      "nick": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "roles": {
+        "items": {
+          "description": "Discord role ID",
+          "pattern": "^\\d{17,20}$",
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "user_id": {
+        "description": "Discord user ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "user_id",
+      "nick",
+      "roles"
+    ],
+    "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

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds the crucial behavioral detail that Discord ignores undefined fields, and it discloses that roles are replaced wholesale. It also specifies the return shape. It does not contradict annotations and provides useful behavioral context beyond what annotations encode, though it could mention permission requirements.

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-organized with bolded section headers (Purpose, When to use, Pass only, Returns). Every sentence delivers value: no filler, no repetition of schema details, and the most important instruction ('Pass only the fields you want to change') is prominent. It is appropriately sized for a complex multi-purpose tool.

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 complexity (10 parameters, multiple distinct operations) and that an output schema exists, the description covers all use cases, alternatives, and behavioral nuances. It mentions the return shape, which is also defined by the output schema, and it clarifies edge cases like null-to-clear and role replacement. Nothing an agent needs to call it correctly is missing.

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 has 100% parameter description coverage, so the baseline is 3. The description goes further by explaining the semantics of passing only needed fields, the wholesale role replacement, and the preference for dedicated role tools. It also clarifies the 'null to clear' convention for several fields, reinforcing schema descriptions. This adds meaningful guidance beyond the schema.

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 ('Modify'), the resource (guild member), and enumerates the exact surface it covers (nick, roles, voice state, timeout). It explicitly names the underlying PATCH endpoint, distinguishing it from siblings like members_add_role and members_remove_role. The purpose is unmistakable and context-rich.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance for each field category and explicitly steers the agent to alternatives for single-role operations ('To add/remove a single role, prefer members_add_role / members_remove_role'). It also clarifies the convention to pass only changed fields. This fully satisfies the dimension.

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

Deploy Server