discord-mcp

discord_get_event_subscribers

Read-only

Lists users who marked 'Interested' in a scheduled Discord event. Returns subscribers and a pagination cursor for fetching more pages.

Instructions

List the users who marked themselves 'Interested' in a scheduled event. Returns { subscribers: [...], nextCursor }. A page holds up to 100 users; if nextCursor is non-null, pass it back as after to fetch the next page. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guild_id": "<guild_id>",
      "event_id": "<event_id>"
    },
    "name": "discord_get_event_subscribers"
  }
}

Input 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	Max subscribers per page (1–100). Default 25.
`event_id`	Yes	ID (snowflake) of the scheduled event.
`guild_id`	Yes	Discord server (guild) ID (snowflake).

Output Schema

Name	Required	Description	Default
`nextCursor`	Yes
`subscribers`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.2.1Nov 7, 2026
- removedOutput schema / properties / nextCursor / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / nextCursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Changed1 schema field changedv2.2.0Sep 6, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed8 schema fields changedv2.0.0Jun 27, 2026

addedInput schema / properties / after / pattern
```
Added value: +"^\\d{17,20}$"
```
addedInput schema / properties / event_id / pattern
```
Added value: +"^\\d{17,20}$"
```
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": {
+    "nextCursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "subscribers": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "avatar": {
+            "type": "string"
+          },
+          "user_id": {
+            "type": "string"
+          },
+          "username": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "user_id",
+          "username",
+          "avatar"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "subscribers",
+    "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: -"Max subscribers to return (1–100). Default 25."New value: +"Max subscribers per page (1–100). Default 25."

Changed3 schema fields changedv1.6.0May 28, 2026

addedInput schema / properties / event_id / description

Added value: +"ID (snowflake) of the scheduled event."

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 subscribers to return (1–100). Default 25."

Addedv1.5.0May 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so 'Read-only' adds little. However, the description goes beyond annotations by disclosing the page size cap (up to 100), the return shape, and the exact cursor round-trip protocol, which is real operational context.

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?

Three tight sentences with the purpose front-loaded and pagination immediately after. The '{ subscribers: [...], nextCursor }' return sketch is mildly redundant given an output schema exists, but it is short enough not to be waste.

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?

With an output schema present and full parameter coverage, the main remaining risk an agent faces is pagination, and that is fully explained. Missing only secondary details such as required bot permissions or the shape of each subscriber entry, which the output schema likely covers.

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 coverage is 100%, so the schema already defines guild_id, event_id, after (with the snowflake pattern), and limit (1-100, default 25). The description's notes on 'after' and the 100-user page size largely restate the schema, so the baseline 3 applies.

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 uses a specific verb+resource+qualifier: list users who marked themselves 'Interested' in a scheduled event. That scope distinguishes it from discord_get_scheduled_event and discord_list_scheduled_events, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the pagination instruction ('if nextCursor is non-null, pass it back as after') tells the agent how to continue but not when to reach for this tool over the other scheduled-event tools. No exclusions or alternatives are named.

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

Deploy Server