discord-mcp

discord_search_members

Read-only

Find Discord server members by matching usernames and nicknames that start with a query; returns their IDs, usernames, nicknames, and roles.

Instructions

Find server members whose username or nickname starts with a query string (prefix match). Returns { members: [...] } with id, username, nickname, roles. Use discord_list_members to page through everyone. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max members to return (1–100). Default 25.
`query`	Yes	Prefix to match against usernames and nicknames.
`guild_id`	Yes	Discord server (guild) ID (snowflake).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`members`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.0Sep 6, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed6 schema fields changedv2.0.0Jun 27, 2026

addedInput schema / properties / guild_id / pattern
```
Added value: +"^\\d{17,20}$"
```
addedInput schema / properties / limit / default
```
Added value: +25
```
addedInput schema / properties / limit / maximum
```
Added value: +100
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "members": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "nickname": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "roles": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "id": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "id",
+                "name"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "username": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "username",
+          "nickname",
+          "roles"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "members"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedv1.6.0May 28, 2026

addedInput schema / properties / guild_id / description

Added value: +"Discord server (guild) ID (snowflake)."

changedInput schema / properties / limit / description

Previous value: -"1–100, default 25."New value: +"Max members to return (1–100). Default 25."

changedInput schema / properties / query / description

Previous value: -"Search query (matches username and nickname)."New value: +"Prefix to match against usernames and nicknames."

Addedv1.5.0May 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations mark the tool as readOnlyHint=true and openWorldHint=true, and the description reinforces 'Read-only.' It also adds useful behavior beyond annotations: prefix matching semantics and the exact member fields returned, which helps an agent predict the call's effect without risking side effects.

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 three short sentences with no filler. It front-loads the purpose, then provides return shape, sibling alternative, and safety trait. Every sentence earns its place.

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 is read-only, has full schema coverage, an output schema, and a clear sibling alternative, the description is complete enough for an agent to select and invoke it correctly. It names the key behavior, return fields, and the paging alternative without needing extra context.

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%, so each parameter is already documented. The description adds no new parameter-level detail; it restates the prefix-match behavior of 'query' and the return shape. This meets the baseline but does not exceed 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 and resource: 'Find server members whose username or nickname starts with a query string (prefix match).' This clearly distinguishes the tool from siblings like discord_list_members and discord_get_member_info by emphasizing prefix matching over pagination or exact lookup.

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 explicitly names the alternative for paging through all members: 'Use discord_list_members to page through everyone.' It gives a clear usage context for when to choose this tool versus a sibling, though it does not cover exclusions such as exact-name lookup or message search.

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

Deploy Server