Discord MCP - Discord server management MCP for AI agents

Create event

create_event

Create a Discord scheduled event—voice, stage, or external—so members see it on the server events list and can mark interest.

Instructions

Create a Discord scheduled community event that members see on the events list and can mark interest in: a voice, stage, or external (in-person or off-platform) event. This is not for sending a message later (use schedule_message) or watching live activity (use subscribe_events). Voice and stage events need a channel; external events need a location and an end time.

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": {
      "name": "<name>",
      "type": "<type>",
      "start_time": "<start_time>"
    },
    "name": "create_event"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`type`	Yes
`guild`	No	Guild (server) name or ID. Omit to use the default guild.
`repeat`	No	Repeat the event. weekly and biweekly recur on the start's weekday; monthly recurs on the same weekday and week of the month.
`channel`	No	Voice or stage channel, for those event types.
`end_time`	No	Required for external events.
`location`	No	Where an external event happens.
`start_time`	Yes	ISO time, like 2026-07-01T19:00:00Z.
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.4.2Nov 12, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedv1.3.0Aug 12, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedv1.1.2Jul 13, 2026

addedInput schema / properties / repeat

Added value: +{
+  "description": "Repeat the event. weekly and biweekly recur on the start's weekday; monthly recurs on the same weekday and week of the month.",
+  "enum": [
+    "daily",
+    "weekly",
+    "biweekly",
+    "monthly"
+  ],
+  "type": "string"
+}

First observedv1.0.2Jun 14, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive creation, and the description adds real value on top by disclosing the type-conditioned input requirements that determine whether a call will succeed. It stops short of stating permission requirements, whether the event is immediately visible to all members, or rate limits, so it is strong but not exhaustive.

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 dense sentences with zero filler, front-loaded with the primary action before the scope clarifications. Every clause carries information an agent needs to route or shape the call.

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 creation tool with no output schema and no annotations covering permissions, the definition covers type-dependent requirements and sibling disambiguation well. It leaves the agent without guidance on what the tool returns (event ID, object) or on required permissions, which are the main remaining gaps.

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?

With schema coverage at 67%, the description compensates by explaining the cross-parameter conditional logic: voice and stage events require a channel, external events require both a location and an end_time. This adds meaning the per-field schema strings only hint at individually. It does not clarify 'repeat' or 'guild' beyond the schema, so it falls short of a 5.

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 opens with a specific verb and resource ('Create a Discord scheduled community event') and immediately enumerates the three event types it produces (voice, stage, external), including a parenthetical clarifying what 'external' means. An agent can distinguish this from schedule_message and subscribe_events without consulting any schema.

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

Usage Guidelines5/5

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

It explicitly states what the tool is NOT for and names the correct sibling for each case: 'not for sending a message later (use schedule_message)' and 'not for watching live activity (use subscribe_events)'. It also gives per-type preconditions (channel for voice/stage, location and end time for external), so the agent knows which call shapes are valid before invoking.

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

Deploy Server