discord-mcp

events_modify

Idempotent

Update an existing Discord scheduled event: reschedule, rename, change location or channel, or transition its status to scheduled, active, completed, or canceled.

Instructions

Purpose: Update fields of an existing scheduled event.

When to use:

Reschedule, rename, change channel/location, or transition status (start/cancel/complete).

Status: 1=SCHEDULED, 2=ACTIVE, 3=COMPLETED, 4=CANCELED. Status transitions are server-validated.

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

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`image`	No
`status`	No	1=SCHEDULED, 2=ACTIVE, 3=COMPLETED, 4=CANCELED
`event_id`	Yes	Scheduled event id
`guild_id`	Yes	Guild that owns the event
`channel_id`	No
`description`	No
`entity_type`	No
`audit_reason`	No	Reason recorded in audit log (X-Audit-Log-Reason header)
`privacy_level`	No
`entity_metadata`	No
`recurrence_rule`	No
`scheduled_end_time`	No
`scheduled_start_time`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.28.0Sep 15, 2026

removedInput schema / properties / image / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / image / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / scheduled_end_time / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / scheduled_end_time / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "channel_id": {
-        "anyOf": [
-          {
-            "description": "Discord channel ID (snowflake)",
-            "pattern": "^\\d{17,20}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "creator_id": {
-        "anyOf": [
-          {
-            "description": "Discord user ID",
-            "pattern": "^\\d{17,20}$",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "entity_type": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      },
-      "guild_id": {
-        "description": "Discord guild (server) ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "id": {
-        "description": "Discord scheduled event ID",
-        "pattern": "^\\d{17,20}$",
-        "type": "string"
-      },
-      "scheduled_end_time": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "scheduled_start_time": {
-        "type": "string"
-      },
-      "status": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      },
-      "untrusted_text": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "guild_id",
-      "scheduled_start_time",
-      "scheduled_end_time",
-      "status",
-      "entity_type",
-      "channel_id",
-      "untrusted_text"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "channel_id": {
+        "anyOf": [
+          {
+            "description": "Discord channel ID (snowflake)",
+            "pattern": "^\\d{17,20}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "creator_id": {
+        "anyOf": [
+          {
+            "description": "Discord user ID",
+            "pattern": "^\\d{17,20}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "entity_type": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "guild_id": {
+        "description": "Discord guild (server) ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "id": {
+        "description": "Discord scheduled event ID",
+        "pattern": "^\\d{17,20}$",
+        "type": "string"
+      },
+      "scheduled_end_time": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "scheduled_start_time": {
+        "type": "string"
+      },
+      "status": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "untrusted_text": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "guild_id",
+      "scheduled_start_time",
+      "scheduled_end_time",
+      "status",
+      "entity_type",
+      "channel_id",
+      "untrusted_text"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate this is a mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds valuable context: status transitions are server-validated, and it details the return shape including caveats about creator_id and untrusted_text. This goes beyond the annotations by explaining validation behavior and return nuances, which is helpful for correct usage.

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 concise, using bold section headers to structure content. It front-loads the purpose, then provides usage guidance, status details, and return information without any fluff. Every sentence adds value, and the formatting improves scannability for an agent.

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?

Given the tool's complexity (14 parameters, nested objects, output schema), the description covers the essential aspects: what it does, when to use, status semantics, and return details. It does not explain every parameter or interaction, but the output schema exists and the description provides enough context for an agent to call it correctly in most scenarios. A more detailed parameter breakdown would be ideal, but the current level is reasonable for an update tool.

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 coverage is only 29%, so the description must compensate for the many undocumented parameters. It does mention status values and that transitions are server-validated, and implies parameters like time, name, and channel through 'reschedule, rename, change channel/location.' However, it does not elaborate on most parameters (e.g., entity_type, entity_metadata, recurrence_rule) or provide syntax details beyond the schema's minimal descriptions. The description adds some meaning but falls short of fully compensating for the low schema coverage.

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 clearly states the tool's purpose: 'Update fields of an existing scheduled event.' This is a specific verb+resource pairing that distinguishes it from siblings like events_create, events_get, and events_delete. It also lists concrete use cases (reschedule, rename, change channel/location, transition status), making the tool's role unambiguous.

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 'When to use' section provides clear scenarios (reschedule, rename, change channel/location, transition status) that tell an agent when to invoke this tool. However, it does not explicitly state when NOT to use it or point to alternative tools (e.g., events_create for new events). The guidance is sufficient for most cases but lacks explicit exclusions.

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

Deploy Server