discord-mcp

events_list_users

Read-onlyIdempotent

Retrieve the list of users who RSVP'd to a scheduled Discord event. Paginate through attendees with before/after cursors and limit results to inspect attendance for any upcoming event.

Instructions

Purpose: List users subscribed (RSVP) to a scheduled event.

When to use:

Inspect attendance/interest for an upcoming event.

Pagination: Use before/after user-id cursors. limit 1-100.

Returns: {users:[{user_id, username, bot, member?}], count, event_id}.

Input Schema

TableJSON Schema

Name	Required	Description
`after`	No	Pagination cursor: users with id > this
`limit`	No	Max users (1-100, default 100)
`before`	No	Pagination cursor: users with id < this
`event_id`	Yes	Scheduled event id
`guild_id`	Yes	Guild that owns the event
`with_member`	No	Include guild member object for each user

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"
-      },
-      "event_id": {
-        "description": "Discord scheduled event ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "users": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "bot": {
-              "type": "boolean"
-            },
-            "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",
-            "bot"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "users",
-      "count",
-      "event_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"
+      },
+      "event_id": {
+        "description": "Discord scheduled event ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "users": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "bot": {
+              "type": "boolean"
+            },
+            "nick": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "user_id": {
+              "description": "Discord user ID",
+              "pattern": "^\\d{17,20}$",
+              "type": "string"
+            },
+            "username": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "user_id",
+            "username",
+            "bot"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "users",
+      "count",
+      "event_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

A3.9/5.0

Behavior3/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds pagination mechanics and return shape, but these largely duplicate what is already in the schema and output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear labels and front-loads the purpose. It is concise, though the pagination and returns sections repeat information already available in the schema and output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is sufficiently described for an agent to call it correctly: required IDs are implied, pagination is mentioned, and return shape is covered by the output schema. Minor caveats like authorization requirements or error behavior are not addressed, but they are not critical for this read-only listing tool.

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 baseline is 3. The description mentions before/after cursors and limit, but the schema already provides equivalent or more detailed descriptions for these parameters.

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 uses a specific verb and resource: 'List users subscribed (RSVP) to a scheduled event.' This clearly differentiates it from sibling tools like events_list or events_get by pinning down exactly what is being listed.

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?

It explicitly states when to use the tool: 'Inspect attendance/interest for an upcoming event.' It does not name alternatives or state when not to use it, but the use case is clear and unambiguous.

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

Deploy Server