Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_create_scheduled_event

Create scheduled events in Discord for voice, stage, or external locations. Provide channel for voice/stage; location and end time for external; returns event name and ID.

Instructions

Create a scheduled event. For 'VOICE'/'STAGE_INSTANCE' events provide channel_id; for 'EXTERNAL' events provide location AND scheduled_end_time. Requires the Manage Events permission. Returns the new event's name and ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesEvent name (max 100 characters).
imageNoOptional cover image URL.
guild_idYesDiscord server (guild) ID (snowflake).
locationNoFree-text location (e.g. a URL or place). Required for EXTERNAL events.
channel_idNoVoice or stage channel ID (snowflake). Required for VOICE/STAGE_INSTANCE events.
descriptionNoOptional event description (max 1000 characters).
entity_typeYesWhere the event happens: 'VOICE' or 'STAGE_INSTANCE' (needs channel_id), or 'EXTERNAL' (needs location + scheduled_end_time).
scheduled_end_timeNoEvent end as an ISO 8601 datetime. Required for EXTERNAL events.
scheduled_start_timeYesEvent start as an ISO 8601 datetime, e.g. '2026-06-01T20:00:00Z'. Must be in the future.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed8 schema fields changedv2.0.0
    • addedInput schema / properties / channel_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)))$"
  3. Changed10 schema fields changedv1.6.0
    • changedInput schema / properties / channel_id / description
      Previous value: -"Voice or stage channel ID. Required for VOICE/STAGE_INSTANCE."New value: +"Voice or stage channel ID (snowflake). Required for VOICE/STAGE_INSTANCE events."
    • addedInput schema / properties / description / description
      Added value: +"Optional event description (max 1000 characters)."
    • changedInput schema / properties / entity_type / description
      Previous value: -"'VOICE', 'STAGE_INSTANCE', or 'EXTERNAL'."New value: +"Where the event happens: 'VOICE' or 'STAGE_INSTANCE' (needs channel_id), or 'EXTERNAL' (needs location + scheduled_end_time)."
    • addedInput schema / properties / entity_type / enum
      Added value: +[
+  "VOICE",
+  "STAGE_INSTANCE",
+  "EXTERNAL"
+]
    • 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: +"Optional cover image URL."
    • changedInput schema / properties / location / description
      Previous value: -"Location string. Required for EXTERNAL events."New value: +"Free-text location (e.g. a URL or place). Required for EXTERNAL events."
    • addedInput schema / properties / name / description
      Added value: +"Event name (max 100 characters)."
    • changedInput schema / properties / scheduled_end_time / description
      Previous value: -"ISO 8601 datetime. Required for EXTERNAL events."New value: +"Event end as an ISO 8601 datetime. Required for EXTERNAL events."
    • changedInput schema / properties / scheduled_start_time / description
      Previous value: -"ISO 8601 datetime (e.g. '2025-06-01T20:00:00Z')."New value: +"Event start as an ISO 8601 datetime, e.g. '2026-06-01T20:00:00Z'. Must be in the future."
  4. Addedv1.5.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description adds that the Manage Events permission is required and that the response contains the new event's name and ID. Annotations already signal mutation (readOnlyHint=false) and non-idempotency, so the description appropriately fills gaps without contradicting them.

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?

Three short sentences with no filler: the action, the key conditional parameter rules, the required permission, and the return value. Everything earns its place and the most important information is front-loaded.

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 9-parameter tool with no output schema and conditional dependencies, the description covers the critical call-time facts: entity-type-specific requirements, the permission gate, and the return payload. The remaining details (max lengths, datetime formats, future-start requirement) are already fully documented in the input schema.

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 coverage is 100%, so the baseline is 3, but the description adds value by synthesizing the conditional parameter relationships: 'VOICE'/'STAGE_INSTANCE' map to channel_id, and 'EXTERNAL' maps to location AND scheduled_end_time. This cross-parameter guidance is more useful than reading each schema property in isolation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource ('Create a scheduled event') and immediately clarifies the event-type branches, so the tool's purpose is unambiguous. It does not explicitly contrast itself with sibling tools like edit/delete, so it stops short of a 5.

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?

It gives clear conditional usage guidance: VOICE/STAGE_INSTANCE events need channel_id, while EXTERNAL events need location and scheduled_end_time, and it states the Manage Events permission prerequisite. It does not mention when-not-to-use or point to alternatives, but the conditions are concrete and actionable.

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