Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_get_event_subscribers

Read-only

Retrieve users interested in a Discord scheduled event. Pass guild and event IDs to list subscribers, with optional limit and cursor pagination for large attendee lists.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor: a user ID (snowflake). Pass the previous response's nextCursor to fetch the next page.
limitNoMax subscribers per page (1–100). Default 25.
event_idYesID (snowflake) of the scheduled event.
guild_idYesDiscord server (guild) ID (snowflake).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextCursorYes
subscribersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed8 schema fields changedv2.0.0
    • 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"
+}
  3. Changed2 schema fields changedv1.7.0
    • 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."
  4. Changed3 schema fields changedv1.6.0
    • 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."
  5. Addedv1.5.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only.' It goes beyond the annotation by disclosing the response shape ({ subscribers: [...], nextCursor }) and the pagination contract, including the 100-user page cap and how to pass nextCursor back as `after`.

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 concise sentences with no filler: the action is front-loaded, the response shape is stated, the pagination rule is actionable, and the read-only safety signal is included. 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?

For a read-only paginated listing tool with a thorough input schema and an output schema, the description covers the essential behavior: what it returns, how paging works, and that it is safe. No critical usage aspect is missing.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining the relationship between the output's nextCursor and the `after` parameter, and by clarifying page-size behavior beyond the schema's default and max values.

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 opens with a specific verb and resource: 'List the users who marked themselves Interested in a scheduled event.' This clearly distinguishes it from sibling event tools like get_scheduled_event and list_scheduled_events, which target event metadata rather than subscriber lists.

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 gives clear context: it is for reading event subscribers, and the pagination instructions explain how to use it across multiple pages. It does not explicitly name alternatives or exclusion conditions, but the operation is specific enough that an agent can infer when to select it.

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

Deploy Server

Other Tools