Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_scheduled_event

Create a stage, voice, or external scheduled event in a Discord server; set start and end times, channel, privacy, image, and location for external events.

Instructions

Create a scheduled event (stage, voice or external). For external events set entity_metadata {location} and scheduled_end_time. [POST /guilds/{guild_id}/scheduled-events]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guild_id": "<guild_id>",
      "name": "<name>",
      "privacy_level": "<privacy_level>",
      "scheduled_start_time": "<scheduled_start_time>",
      "entity_type": "<entity_type>"
    },
    "name": "create_guild_scheduled_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName
imageNoImage: local file path, http(s) URL or data: URI
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
channel_idNoChannel ID
descriptionNoDescription
entity_typeYesEvent type: 1 = stage, 2 = voice, 3 = external (somewhere else)
privacy_levelYesPrivacy level: 2 = guild only
entity_metadataNoFor external events: {"location": "..."}
recurrence_ruleNo
scheduled_end_timeNoEnd time (ISO8601, required for external events) (ISO8601 time)
scheduled_start_timeYesStart time (ISO8601) (ISO8601 time)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the description's main added value is the external-event requirement and the POST endpoint, which confirms a write against Discord. It does not disclose permission requirements, whether creation notifies members, or what the call returns (there is no output schema), leaving real behavioral gaps.

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 plus the endpoint tag, with the core purpose front-loaded and the conditional special case immediately after. Every clause carries information; no filler or restatement of the tool name alone.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, 5-required creation tool with no output schema, the definition covers the tricky external-event case but says nothing about the returned object, required permissions, or side effects such as invite/notification behavior. Given that the schema itself documents most parameters, this is adequate but visibly incomplete.

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 already 92%, so the baseline is 3, but the description goes beyond it by stating a cross-field constraint the schema only repeats piecemeal: external events need both entity_metadata {location} and scheduled_end_time, and it maps the parenthetical variants to the numeric entity_type values. It adds nothing about recurrence_rule or privacy_level beyond the schema.

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?

States a specific verb and resource ('Create a scheduled event') plus the three supported event variants (stage, voice or external), so an agent can immediately distinguish this from the sibling list/get/modify/delete event tools. It stops short of naming any alternative explicitly, which keeps it out of the top band.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a useful conditional rule: external events require entity_metadata {location} and scheduled_end_time. However, it gives no guidance on when to use this tool versus create_guild_scheduled_event_exception (recurrence) or on any prerequisites such as permission to manage events, so usage is only implied.

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