discord-mcp

threads_list_members

Read-onlyIdempotent

List members of a Discord thread to audit private thread access or build mention lists. Provides user IDs, join timestamps, and flags with pagination support.

Instructions

Purpose: List members of a thread.

When to use:

Audit who is in a private thread; build mention lists.

Pagination: Discord requires the GUILD_MEMBERS privileged intent for with_member=true. after is a snowflake cursor.

Returns: {members:[{user_id, join_timestamp, flags}], count, thread_id}.

Input Schema

TableJSON Schema

Name	Required	Description
`after`	No	Pagination cursor: get members with id > this
`limit`	No	Max results (1-100, default 100)
`thread_id`	Yes	Thread to list members for
`with_member`	No	Whether Discord should hydrate the underlying guild member object

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": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      },
-      "members": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "flags": {
-              "anyOf": [
-                {
-                  "maximum": 9007199254740991,
-                  "minimum": -9007199254740991,
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "join_timestamp": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "user_id": {
-              "anyOf": [
-                {
-                  "description": "Discord user ID",
-                  "pattern": "^\\d{17,20}$",
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "required": [
-            "user_id",
-            "join_timestamp",
-            "flags"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "thread_id": {
-        "description": "Discord channel ID (snowflake)",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "members",
-      "count",
-      "thread_id"
-    ],
-    "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": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "members": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "flags": {
+              "anyOf": [
+                {
+                  "maximum": 9007199254740991,
+                  "minimum": -9007199254740991,
+                  "type": "integer"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "join_timestamp": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "user_id": {
+              "anyOf": [
+                {
+                  "description": "Discord user ID",
+                  "pattern": "^\\d{17,20}$",
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            }
+          },
+          "required": [
+            "user_id",
+            "join_timestamp",
+            "flags"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "thread_id": {
+        "description": "Discord channel ID (snowflake)",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "members",
+      "count",
+      "thread_id"
+    ],
+    "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?

With readOnlyHint, idempotentHint, and destructiveHint already provided, the description adds value by disclosing that with_member=true requires the Discord GUILD_MEMBERS privileged intent, which is a non-obvious environmental prerequisite. It also states that 'after' is a snowflake cursor and provides the return shape, giving useful behavioral context beyond the annotations.

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 compact and well-organized with bold section labels. Purpose, usage, pagination caveat, and return shape are each covered in minimal, scannable text with no filler or repetition of schema content.

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 this tool's complexity. It provides purpose, usage context, an important intent requirement, pagination guidance, and the return format. The input schema and annotations cover the rest, so nothing critical is missing for an agent to call it correctly.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful semantics by explaining that with_member=true is gated on the GUILD_MEMBERS privileged intent, which is not mentioned in the schema. It also reinforces that 'after' is a snowflake cursor, slightly expanding on the schema's pagination phrase.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear verb-resource pairing: 'List members of a thread.' It further clarifies intent with 'Audit who is in a private thread; build mention lists.' It does not explicitly contrast itself with sibling tools like threads_get_member or members_list, but the resource scope ('of a thread') makes the purpose unambiguous.

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?

A dedicated 'When to use' section gives concrete use cases: auditing private thread membership and building mention lists. It does not mention when not to use it or point to an alternative tool, but the listed contexts are clear enough for an agent to select this tool appropriately.

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

Deploy Server