discord-mcp

users_get

Read-onlyIdempotent

Look up a public Discord user profile by user ID to retrieve username, avatar, and bot status.

Instructions

Purpose: Look up a public user profile by id (/users/{user.id}).

When to use:

Resolve a username/avatar for a user id surfaced by another tool.

When NOT to use:

Fetching guild-specific member info → members_get. Bot identity → users_get_current.

Returns: {id, username, global_name, avatar, bot, untrusted_text}. Names remain raw Discord data; untrusted_text provides a separately fenced copy.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user_id`	Yes	Discord user id

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": {
-      "avatar": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "bot": {
-        "type": "boolean"
-      },
-      "global_name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "id": {
-        "description": "Discord user ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "untrusted_text": {
-        "type": "string"
-      },
-      "username": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "username",
-      "global_name",
-      "avatar",
-      "bot",
-      "untrusted_text"
-    ],
-    "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": {
+      "avatar": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "bot": {
+        "type": "boolean"
+      },
+      "global_name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Discord user ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "untrusted_text": {
+        "type": "string"
+      },
+      "username": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "username",
+      "global_name",
+      "avatar",
+      "bot",
+      "untrusted_text"
+    ],
+    "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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds value by explaining the raw Discord data nature and the separately fenced untrusted_text field, which is important context for downstream handling.

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 tightly organized with clear bolded sections, front-loaded purpose, and no redundant sentences. Every section earns its place and the entire description is compact.

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?

For a simple lookup tool with one parameter, full schema coverage, an output schema, and comprehensive annotations, the description covers purpose, usage boundaries, and return-value trust concerns. Nothing essential is missing.

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?

The schema has 100% description coverage for the single parameter, so the baseline is 3. The description adds the useful context that the id likely comes from another tool, but does not add material format or semantics beyond what the schema already states.

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 and resource: 'Look up a public user profile by id'. It also explicitly distinguishes itself from sibling tools in the 'When NOT to use' section by naming members_get and users_get_current, so an agent can tell them apart.

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?

It clearly states when to use the tool: 'Resolve a username/avatar for a user id surfaced by another tool.' It also gives explicit exclusions and alternatives for guild-specific member info and bot identity, leaving no ambiguity about selection.

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

Deploy Server