discord-mcp

voice_get_user_state

Read-onlyIdempotent

Fetch a member's voice status in a Discord guild, returning channel, mute/deaf flags, and request-to-speak timestamp. Use it to verify if a user is in voice and their state.

Instructions

Purpose: Fetch a user's voice state in a guild (/guilds/{guild.id}/voice-states/{user.id}).

Returns: voice state shape (channel, mute/deaf flags, request_to_speak_timestamp).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user_id`	Yes	Member whose voice state to fetch
`guild_id`	Yes	Guild to query

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.28.0Sep 15, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "channel_id": {
-        "anyOf": [
-          {
-            "description": "Discord channel ID (snowflake)",
-            "pattern": "^\\d{17,20}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "deaf": {
-        "type": "boolean"
-      },
-      "guild_id": {
-        "description": "Discord guild (server) ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "mute": {
-        "type": "boolean"
-      },
-      "request_to_speak_timestamp": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "self_deaf": {
-        "type": "boolean"
-      },
-      "self_mute": {
-        "type": "boolean"
-      },
-      "self_stream": {
-        "type": "boolean"
-      },
-      "self_video": {
-        "type": "boolean"
-      },
-      "session_id": {
-        "type": "string"
-      },
-      "suppress": {
-        "type": "boolean"
-      },
-      "user_id": {
-        "description": "Discord user ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "guild_id",
-      "channel_id",
-      "user_id",
-      "session_id",
-      "deaf",
-      "mute",
-      "self_deaf",
-      "self_mute",
-      "self_video",
-      "suppress",
-      "request_to_speak_timestamp"
-    ],
-    "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": {
+      "channel_id": {
+        "anyOf": [
+          {
+            "description": "Discord channel ID (snowflake)",
+            "pattern": "^\\d{17,20}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "deaf": {
+        "type": "boolean"
+      },
+      "guild_id": {
+        "description": "Discord guild (server) ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "mute": {
+        "type": "boolean"
+      },
+      "request_to_speak_timestamp": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "self_deaf": {
+        "type": "boolean"
+      },
+      "self_mute": {
+        "type": "boolean"
+      },
+      "self_stream": {
+        "type": "boolean"
+      },
+      "self_video": {
+        "type": "boolean"
+      },
+      "session_id": {
+        "type": "string"
+      },
+      "suppress": {
+        "type": "boolean"
+      },
+      "user_id": {
+        "description": "Discord user ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "guild_id",
+      "channel_id",
+      "user_id",
+      "session_id",
+      "deaf",
+      "mute",
+      "self_deaf",
+      "self_mute",
+      "self_video",
+      "suppress",
+      "request_to_speak_timestamp"
+    ],
+    "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/5.0

Behavior3/5

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint=false, so the description does not need to restate safety. It adds a brief summary of the returned voice state shape, which is useful context, but it does not disclose edge cases like a null response when the user has no voice state.

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 compact and well-structured with 'Purpose' and 'Returns' sections. Every sentence provides useful information, and the main purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup with two required parameters, annotations, and an output schema, the description is largely complete. The only minor gap is not mentioning that a user may have no voice state and the result could be null, but the presence of an output schema mitigates this.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and both parameters have clear descriptions ('Member whose voice state to fetch' and 'Guild to query'). The description adds the endpoint path but no additional meaning or constraints beyond what the schema already provides.

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 ('Fetch'), a specific resource ('a user's voice state in a guild'), and the exact endpoint path. This clearly differentiates it from sibling tools like voice_get_current_user_state and makes its scope obvious.

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

Usage Guidelines4/5

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

The description makes the intended usage clear: fetch a specific user's voice state by guild and user ID. It does not explicitly name alternatives or exclusion conditions, but the endpoint path and wording provide enough context to avoid confusing it with current-user or modification tools.

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

Deploy Server