Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_edit_scheduled_event

Idempotent

Update Discord scheduled event details like name, time, or location, and manage its status by starting, completing, or canceling it when allowed.

Instructions

Update a scheduled event; only provided fields change. Use the status field to start ('ACTIVE'), end ('COMPLETED'), or cancel ('CANCELED') an event; Discord only allows certain status transitions. Requires the Manage Events permission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew event name (max 100 characters).
imageNoNew cover image URL.
statusNoChange event status. Allowed transitions only: SCHEDULED→ACTIVE→COMPLETED, or SCHEDULED→CANCELED (no transition back to SCHEDULED exists).
event_idYesID (snowflake) of the event to edit.
guild_idYesDiscord server (guild) ID (snowflake).
locationNoNew free-text location for EXTERNAL events.
channel_idNoNew voice/stage channel ID (snowflake) for VOICE/STAGE_INSTANCE events.
descriptionNoNew event description (max 1000 characters).
scheduled_end_timeNoNew end time as an ISO 8601 datetime.
scheduled_start_timeNoNew start time as an ISO 8601 datetime.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed11 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / event_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / guild_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / image / format
      Added value: +"uri"
    • addedInput schema / properties / image / pattern
      Added value: +"^https?://"
    • addedInput schema / properties / scheduled_end_time / format
      Added value: +"date-time"
    • addedInput schema / properties / scheduled_end_time / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    • addedInput schema / properties / scheduled_start_time / format
      Added value: +"date-time"
    • addedInput schema / properties / scheduled_start_time / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    • changedInput schema / properties / status / description
      Previous value: -"Change event status. Allowed transitions only: SCHEDULED→ACTIVE→COMPLETED, or SCHEDULED→CANCELED."New value: +"Change event status. Allowed transitions only: SCHEDULED→ACTIVE→COMPLETED, or SCHEDULED→CANCELED (no transition back to SCHEDULED exists)."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "SCHEDULED",
-  "ACTIVE",
-  "COMPLETED",
-  "CANCELED"
-]New value: +[
+  "ACTIVE",
+  "COMPLETED",
+  "CANCELED"
+]
  3. Changed11 schema fields changedv1.6.0
    • addedInput schema / properties / channel_id / description
      Added value: +"New voice/stage channel ID (snowflake) for VOICE/STAGE_INSTANCE events."
    • addedInput schema / properties / description / description
      Added value: +"New event description (max 1000 characters)."
    • addedInput schema / properties / event_id / description
      Added value: +"ID (snowflake) of the event to edit."
    • addedInput schema / properties / guild_id / description
      Added value: +"Discord server (guild) ID (snowflake)."
    • changedInput schema / properties / image / description
      Previous value: -"Cover image URL."New value: +"New cover image URL."
    • addedInput schema / properties / location / description
      Added value: +"New free-text location for EXTERNAL events."
    • addedInput schema / properties / name / description
      Added value: +"New event name (max 100 characters)."
    • changedInput schema / properties / scheduled_end_time / description
      Previous value: -"ISO 8601 datetime."New value: +"New end time as an ISO 8601 datetime."
    • changedInput schema / properties / scheduled_start_time / description
      Previous value: -"ISO 8601 datetime."New value: +"New start time as an ISO 8601 datetime."
    • changedInput schema / properties / status / description
      Previous value: -"'SCHEDULED', 'ACTIVE', 'COMPLETED', or 'CANCELED'."New value: +"Change event status. Allowed transitions only: SCHEDULED→ACTIVE→COMPLETED, or SCHEDULED→CANCELED."
    • addedInput schema / properties / status / enum
      Added value: +[
+  "SCHEDULED",
+  "ACTIVE",
+  "COMPLETED",
+  "CANCELED"
+]
  4. Addedv1.5.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate this is a mutating, non-destructive, idempotent operation. The description adds valuable behavioral context beyond those hints: partial-field update semantics, status-transition restrictions, and the Manage Events permission requirement. This is meaningfully richer than the structured annotations alone.

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?

Two sentences, front-loaded with the core action and update semantics, followed by the status-transition guidance and permission requirement. No filler or repetition of schema content.

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 complex mutation tool with 10 parameters and no output schema, the description covers the essential behavioral and permission context. Schema descriptions handle individual parameter meanings. It could be slightly more explicit about alternative tools, but it is complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description goes beyond the schema by clarifying update semantics ('only provided fields change') and giving practical guidance on using the status field to control the event lifecycle. This adds meaning to the parameters collectively.

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 names a specific verb ('Update') and resource ('a scheduled event'), and adds the key semantic 'only provided fields change'. This clearly distinguishes it from sibling tools like discord_create_scheduled_event and discord_delete_scheduled_event.

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 provides clear guidance on when to use the status field for starting, ending, or canceling an event, and warns that Discord only allows certain transitions. It does not explicitly name alternatives like delete for removal, but the context is strong enough for an agent to infer the right tool.

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

Deploy Server

Other Tools