discord-mcp

discord_list_members

Read-only

Fetch Discord server members with their roles, ordered by user ID, using pagination for large servers. Pass the returned cursor to retrieve the next page.

Instructions

List members of a server with their roles, ordered by user ID. Returns { members: [...], nextCursor }. A page holds up to 1000 members; if nextCursor is non-null, pass it back as after to fetch the next page. Use discord_search_members to find specific members by name, or discord_get_member_info for one member's full details. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`after`	No	Pagination cursor: a user ID (snowflake). Pass the previous response's nextCursor to fetch the next page.
`limit`	No	How many members per page (1–1000). Default 50.
`guild_id`	Yes	Discord server (guild) ID (snowflake).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`members`	Yes
`nextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed7 schema fields changedv2.0.0Jun 27, 2026

addedInput schema / properties / after / pattern
```
Added value: +"^\\d{17,20}$"
```
addedInput schema / properties / guild_id / pattern
```
Added value: +"^\\d{17,20}$"
```
addedInput schema / properties / limit / default
```
Added value: +50
```
addedInput schema / properties / limit / maximum
```
Added value: +1000
```
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"
+          },
+          "joinedAt": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "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",
+          "joinedAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextCursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "members",
+    "nextCursor"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv1.7.0May 29, 2026

addedInput schema / properties / after

Added value: +{
+  "description": "Pagination cursor: a user ID (snowflake). Pass the previous response's nextCursor to fetch the next page.",
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"How many members to return (1–1000). Default 50."New value: +"How many members per page (1–1000). Default 50."

Changed2 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–1000, default 50."New value: +"How many members to return (1–1000). Default 50."

Addedv1.5.0May 8, 2026
Removedv1.0.0May 1, 2026
First observedv0.1.0Mar 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses pagination behavior (page size up to 1000, nextCursor semantics), ordering by user ID, and the exact return shape. It also explicitly states 'Read-only,' which is consistent with the annotation and adds behavioral clarity. There is no contradiction.

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 tightly packed sentences, each earning its place: the core purpose, the pagination behavior, and the routing to sibling tools. It is front-loaded with the primary action and contains zero filler, making it easy to parse quickly.

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 description is complete for a paginated list tool. It covers what is returned, how pagination works, and which sibling tools to use for alternative needs. Since an output schema exists, it need not detail return fields further, and the annotations already cover the read-only safety profile. Nothing necessary for correct invocation 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?

Schema description coverage is 100%, so the schema already explains all three parameters. The description's pagination note about nextCursor mirrors the `after` parameter's schema description, and 'page holds up to 1000 members' restates the `limit` maximum. It does not add substantial new parameter-level meaning beyond what the schema already provides, so the baseline of 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?

States a specific verb and resource: 'List members of a server with their roles.' It also specifies ordering by user ID, and differentiates itself from siblings by naming discord_search_members and discord_get_member_info as alternatives. Even the title 'List members' aligns perfectly with the description.

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?

Explicitly says when to use alternatives: 'Use discord_search_members to find specific members by name, or discord_get_member_info for one member's full details.' It also gives clear pagination guidance: pass nextCursor back as `after` for the next page. This leaves no ambiguity about when this tool is appropriate.

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

Deploy Server