discord-mcp

members_search

Read-onlyIdempotent

Fuzzy-search Discord guild members by username or nickname prefix to convert names into snowflake IDs. Provide guild ID and query; returns matching user IDs, usernames, and nicknames.

Instructions

Purpose: Fuzzy-search guild members by username/nick prefix.

When to use: convert "find @alice" or "users named bob" into snowflake IDs.

Example: {guild_id:"999000999000999000", query:"alice", limit:25}

Returns: {matches:[{user_id, username, global_name, nick}], count}.

Rate limit: 5/sec/guild.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max matches (1-1000, default 25)
`query`	Yes	Username/nick prefix or substring
`guild_id`	Yes	Guild to search

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": {
-      "count": {
-        "type": "number"
-      },
-      "matches": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "global_name": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "nick": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "user_id": {
-              "description": "Discord user ID",
-              "pattern": "^\\d{17,20}$",
-              "type": "string"
-            },
-            "username": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "user_id",
-            "username",
-            "global_name",
-            "nick"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "matches",
-      "count"
-    ],
-    "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": {
+      "count": {
+        "type": "number"
+      },
+      "matches": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "global_name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "nick": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "user_id": {
+              "description": "Discord user ID",
+              "pattern": "^\\d{17,20}$",
+              "type": "string"
+            },
+            "username": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "user_id",
+            "username",
+            "global_name",
+            "nick"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "matches",
+      "count"
+    ],
+    "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

Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds meaningful context beyond that: a rate limit of 5/sec/guild, fuzzy matching semantics, and a concrete return shape with matches and count. No contradiction with annotations exists.

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 structured with labeled sections: Purpose, When to use, Example, Returns, and Rate limit. Every section earns its place, and the most important info is front-loaded.

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?

The combination of schema, annotations, and description covers what the tool does, when to use it, how to call it, what it returns, and its rate limit. Nothing essential is missing for an agent to correctly select and invoke this tool.

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?

Schema coverage is 100%, so each parameter is already documented. The description adds value with a worked example showing realistic values, clarifies that query is meant for username/nick matching, and describes the output fields that link to parameters. This is more than the baseline for fully covered schemas.

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: 'Fuzzy-search guild members by username/nick prefix.' It also clarifies the practical outcome, converting user references like 'find @alice' into snowflake IDs, which distinguishes it from sibling tools like members_list and members_get.

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 'When to use' section gives clear, concrete context: converting mentions or partial names into snowflake IDs. It does not explicitly name alternative tools or exclusions, but the guidance is specific enough for an agent to route this kind of lookup correctly.

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

Deploy Server