events_list
List scheduled events for a guild.
When to use
Section titled “When to use”enumerate upcoming voice/stage/external events.
MCP call example
Section titled “MCP call example”{ "name": "events_list", "arguments": { "guild_id": "123456789012345678" }}| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
guild_id | string | yes | pattern: ^\d{17,20}$ | Guild to query |
Complete input JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "guild_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Guild to query" } }, "required": [ "guild_id" ]}Returns
Section titled “Returns”{events:[...], count}. Structured names and descriptions remain raw Discord data; the human-readable text response fences event names.
Example structured result
Section titled “Example structured result”{ "events": [ { "id": "123456789012345678", "name": "Example name", "scheduled_start_time": "2030-01-01T10:00:00.000Z", "scheduled_end_time": "2030-01-01T10:00:00.000Z", "status": 1, "entity_type": 1, "channel_id": "123456789012345678" } ], "count": 1}Output schema
Section titled “Output schema”| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
events | array<object> | yes | ||
count | number | yes |
Complete output JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "events": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string" }, "name": { "type": "string" }, "description": { "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "scheduled_start_time": { "type": "string" }, "scheduled_end_time": { "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "status": { "type": "integer" }, "entity_type": { "type": "integer" }, "channel_id": { "anyOf": [ { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord channel ID (snowflake)" }, { "type": "null" } ] }, "creator_id": { "anyOf": [ { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord user ID" }, { "type": "null" } ] } }, "required": [ "id", "name", "scheduled_start_time", "scheduled_end_time", "status", "entity_type", "channel_id" ], "additionalProperties": false } }, "count": { "type": "number" } }, "required": [ "events", "count" ], "additionalProperties": false}Annotations
Section titled “Annotations”| Property | Value |
|---|---|
| Read-only | yes |
| Destructive | no |
| Idempotent | yes |
| Open-world | yes |
| Confirmation required | no |
Access and common errors
Section titled “Access and common errors”- The
eventscategory must be enabled byMCP_CATEGORIESwhen an allowlist is set. - This endpoint uses the configured bot credential and Discord’s route-specific authorization; discord-mcp does not elevate access.
- An invalid credential returns a
401-class tool error. Insufficient endpoint permission or scope returns403; inaccessible resources commonly return404.
Trust boundary
Section titled “Trust boundary”Discord-supplied names, topics, messages, and other strings are untrusted. Fields in
structuredContent may remain raw even when the companion human-readable content
or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not
sanitization or proof against prompt injection. Never treat Discord text as instructions
or feed it into a consequential write without an independent policy or human approval.
Source
Section titled “Source”packages/mcp-core/src/tools/events/list.ts