discord-mcp

discord_get_scheduled_event

Read-only

Retrieve complete details for any Discord scheduled event: name, description, status, type, channel/location, start/end times, creator, and interested-user count. Read-only, returns JSON.

Instructions

Get full details for one scheduled event: name, description, status, type, channel/location, start/end times, creator, and interested-user count. Read-only. Returns a JSON object.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`event_id`	Yes	ID (snowflake) of the scheduled event.
`guild_id`	Yes	Discord server (guild) ID (snowflake).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`image`	Yes
`status`	Yes
`location`	Yes
`channel_id`	Yes
`creator_id`	Yes
`user_count`	Yes
`description`	Yes
`entity_type`	Yes
`scheduled_end_time`	Yes
`scheduled_start_time`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.2.0Sep 6, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed3 schema fields changedv2.0.0Jun 27, 2026

addedInput schema / properties / event_id / pattern
```
Added value: +"^\\d{17,20}$"
```
addedInput schema / properties / guild_id / pattern
```
Added value: +"^\\d{17,20}$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "channel_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "creator_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "description": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "entity_type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        }
+      ]
+    },
+    "id": {
+      "type": "string"
+    },
+    "image": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "location": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "scheduled_end_time": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "scheduled_start_time": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        }
+      ]
+    },
+    "user_count": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "description",
+    "status",
+    "entity_type",
+    "channel_id",
+    "location",
+    "scheduled_start_time",
+    "scheduled_end_time",
+    "creator_id",
+    "user_count",
+    "image"
+  ],
+  "type": "object"
+}

Changed2 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)."
```
Addedv1.5.0May 8, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The readOnlyHint annotation already covers the safety profile, so the description's 'Read-only' statement adds no new behavioral information. It does disclose that the result is a JSON object and lists the fields returned, but it does not address error behavior, permissions, or rate limits. This is acceptable for a read-only getter but not richly transparent.

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?

The description is compact and front-loaded with the action and resource. Statements like 'Read-only' and 'Returns a JSON object' are somewhat redundant given the annotations and output schema, but the overall size is appropriate and there is no fluff or ambiguity.

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?

For a simple read-only getter with a full input schema, an output schema, and a readOnlyHint annotation, the description is mostly complete. It lists the key returned fields and clearly indicates scope, though it does not mention potential failure cases or permission requirements. These omissions are minor for this tool complexity.

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%, so both parameters (guild_id and event_id) are already fully documented in the schema. The description does not add parameter-specific guidance beyond indicating that it operates on one scheduled event, which does not raise the score above the baseline.

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 states a specific verb ('Get'), a specific resource ('one scheduled event'), and enumerates the exact details returned. It is easily distinguished from sibling tools like discord_list_scheduled_events, discord_create_scheduled_event, and discord_get_event_subscribers because it clearly targets a single event's full details.

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 clearly implies when to use it: when the agent needs full details for a single scheduled event, identified by guild_id and event_id. It does not explicitly name alternative tools or state when not to use it, so it stops short of a perfect 5.

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

Deploy Server