events_get

Events Read only

Fetch a single scheduled event by id.

When to use

Inspect a specific event before modifying or deleting.

MCP call example

{
  "name": "events_get",
  "arguments": {
    "guild_id": "123456789012345678",
    "event_id": "123456789012345678"
  }
}

Input

Field	Type	Required	Constraints	Description
`guild_id`	string	yes	pattern: `^\d{17,20}$`	Guild that owns the event
`event_id`	string	yes	pattern: `^\d{17,20}$`	Scheduled event id
`with_user_count`	boolean	no		Include `user_count` in response

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 that owns the event"
    },
    "event_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Scheduled event id"
    },
    "with_user_count": {
      "description": "Include `user_count` in response",
      "type": "boolean"
    }
  },
  "required": [
    "guild_id",
    "event_id"
  ]
}

Returns

projected event shape with optional user_count. creator_id is absent for events created before October 2021. Event text remains raw; untrusted_text provides a separately fenced copy.

Example structured result

{
  "id": "123456789012345678",
  "guild_id": "123456789012345678",
  "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",
  "untrusted_text": "example"
}

Output schema

Field	Type	Required	Constraints	Description
`id`	string	yes	pattern: `^\d{17,20}$`	Discord scheduled event ID
`guild_id`	string	yes	pattern: `^\d{17,20}$`	Discord guild (server) ID
`scheduled_start_time`	string	yes
`scheduled_end_time`	string \| null	yes
`status`	integer	yes
`entity_type`	integer	yes
`channel_id`	string \| null	yes
`creator_id`	string \| null	no
`user_count`	integer	no
`untrusted_text`	string	yes

Complete output JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Discord scheduled event ID"
    },
    "guild_id": {
      "type": "string",
      "pattern": "^\\d{17,20}$",
      "description": "Discord guild (server) ID"
    },
    "scheduled_start_time": {
      "type": "string"
    },
    "scheduled_end_time": {
      "type": [
        "string",
        "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"
        }
      ]
    },
    "user_count": {
      "type": "integer"
    },
    "untrusted_text": {
      "type": "string"
    }
  },
  "required": [
    "id",
    "guild_id",
    "scheduled_start_time",
    "scheduled_end_time",
    "status",
    "entity_type",
    "channel_id",
    "untrusted_text"
  ],
  "additionalProperties": false
}

Annotations

Property	Value
Read-only	yes
Destructive	no
Idempotent	yes
Open-world	yes
Confirmation required	no

Access and common errors

The events category must be enabled by MCP_CATEGORIES when an allowlist is set.
Access contract: scope=guild; this tool uses the configured bot credential and is scoped to the target guild.
No named Discord permission bit is asserted by this contract.
Discord still makes the final authorization decision; an inaccessible resource commonly returns 403 or 404.

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

packages/mcp-core/src/tools/events/get.ts