Skip to main content
Glama
scarecr0w12

discord-mcp

get_event_subscribers

Retrieve users subscribed to a Discord scheduled event by providing the guild and event IDs. This tool helps manage event attendance and participant lists.

Instructions

Get users subscribed to a scheduled event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guildIdYesThe ID of the server (guild)
eventIdYesThe ID of the event
limitNoMax users to fetch (default 100)

Implementation Reference

  • Complete implementation of the 'get_event_subscribers' MCP tool, including registration, input schema using Zod, and handler logic that fetches Discord scheduled event subscribers using event.fetchSubscribers() with error handling.
    server.tool(
      'get_event_subscribers',
      'Get users subscribed to a scheduled event',
      {
        guildId: z.string().describe('The ID of the server (guild)'),
        eventId: z.string().describe('The ID of the event'),
        limit: z.number().optional().describe('Max users to fetch (default 100)'),
      },
      async ({ guildId, eventId, limit = 100 }) => {
        const result = await withErrorHandling(async () => {
          const client = await getDiscordClient();
          const guild = await client.guilds.fetch(guildId);
          const event = await guild.scheduledEvents.fetch(eventId);
          const subscribers = await event.fetchSubscribers({ limit, withMember: true });
    
          return subscribers.map((sub) => ({
            id: sub.user.id,
            username: sub.user.username,
            member: sub.member ? {
              nickname: sub.member.nickname,
              joinedAt: sub.member.joinedAt?.toISOString(),
            } : null,
          }));
        });
    
        if (!result.success) {
          return { content: [{ type: 'text', text: result.error }], isError: true };
        }
    
        return { content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }] };
      }
    );
  • src/index.ts:63-63 (registration)
    Main server initialization calls registerEventTools(server), which registers all event management tools including 'get_event_subscribers'.
    registerEventTools(server);
  • src/index.ts:20-20 (registration)
    Imports the registerEventTools function used to register the event tools module containing 'get_event_subscribers'.
    import { registerEventTools } from './tools/event-tools.js';
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states a read operation ('Get') but doesn't mention permissions required, rate limits, pagination behavior (beyond the 'limit' parameter), or what the return format looks like. For a tool fetching user data, this leaves significant behavioral gaps.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a straightforward read operation.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what data is returned about subscribers (e.g., user objects with IDs/names), whether results are paginated beyond the limit parameter, or any error conditions. The context signals indicate this is a read operation, but more behavioral context is needed.

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%, with all three parameters clearly documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema (guildId, eventId, limit with default). This meets the baseline expectation when schema coverage is complete.

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 clearly states the verb 'Get' and resource 'users subscribed to a scheduled event', making the purpose unambiguous. It doesn't explicitly differentiate from sibling tools like 'get_event_info' or 'list_members', but the specific focus on event subscribers is clear enough for basic understanding.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_event_info' (for event details) or 'list_members' (for general server members). There's no mention of prerequisites, limitations, or comparison with sibling tools, leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scarecr0w12/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server