discord-mcp

members_get

Read-onlyIdempotent

Fetch a Discord guild member by user ID to retrieve roles, nickname, join date, and account status.

Instructions

Purpose: Fetch a guild member by user ID.

When to use: inspect roles, nick, joined-at of a known user.

Returns: {user_id, username, global_name, nick, roles, joined_at, premium_since?, pending?}. joined_at may be null; premium_since and pending are absent when Discord omits them. Structured nick remains raw Discord data; the human-readable text response fences it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user_id`	Yes	Member to fetch
`guild_id`	Yes	Guild containing the member

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": {
-      "global_name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "joined_at": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "nick": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "pending": {
-        "type": "boolean"
-      },
-      "premium_since": {
-        "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"
-      },
-      "username": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "user_id",
-      "username",
-      "global_name",
-      "nick",
-      "roles",
-      "joined_at"
-    ],
-    "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": {
+      "global_name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "joined_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "nick": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "pending": {
+        "type": "boolean"
+      },
+      "premium_since": {
+        "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"
+      },
+      "username": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "user_id",
+      "username",
+      "global_name",
+      "nick",
+      "roles",
+      "joined_at"
+    ],
+    "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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuine behavioral nuance beyond that: `joined_at` may be null, `premium_since` and `pending` are absent (not just null) when Discord omits them, and the structured `nick` differs from the fenced text-rendered version. The 'fences it' phrasing is slightly cryptic but still conveys a real structured-vs-text output distinction.

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?

Three labeled sections (Purpose, When to use, Returns) with the purpose front-loaded. Every sentence earns its place: nullability, optional-field absence semantics, and the text-fencing caveat are each materially useful. No filler or repetition of schema contents.

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 low-complexity 2-param read operation, the definition is nearly complete: schema covers both params, annotations cover the safety profile, an output schema exists, and the description explains return-value edge cases. Minor omissions are error behavior (e.g., member not found) and auth expectations, which are secondary for a read-only fetch.

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 coverage is 100% — both user_id and guild_id have descriptions in the schema. The description reinforces user_id as the lookup key for a known user but adds no format, pattern, or syntax detail beyond what the schema already provides. The baseline 3 is appropriate.

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 Purpose section states a specific verb+resource+scope: 'Fetch a guild member by user ID.' This cleanly distinguishes it from siblings like members_list, members_search, members_get_current_user, and members_get_ban, and the mentioned fields (roles, nick, joined-at) further pin down its role.

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?

'When to use: inspect roles, nick, joined-at of a known user' provides a clear usage context, and the 'known user' phrasing implicitly signals that user_id must already be available (otherwise search would be needed). However, it stops short of naming explicit alternatives or exclusion criteria, which would warrant a 5.

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

Deploy Server