Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_scheduled_event

Edit a Discord guild scheduled event or start, end, or cancel it by updating event details such as name, time, channel, and status.

Instructions

Edit or start/end/cancel an event (status: 2 active, 3 completed, 4 cancelled). [PATCH /guilds/{guild_id}/scheduled-events/{event_id}]

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>",
      "event_id": "<event_id>"
    },
    "name": "modify_guild_scheduled_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName
imageNoImage: local file path, http(s) URL or data: URI
reasonNoReason (shown in the audit log)
statusNo2 active, 3 completed, 4 cancelled
event_idYesScheduled event ID
guild_idYesServer (guild) ID
channel_idNo
descriptionNo
entity_typeNoEvent type: 1 = stage, 2 = voice, 3 = external (somewhere else)
privacy_levelNoPrivacy level: 2 = guild only
entity_metadataNo
recurrence_ruleNo
scheduled_end_timeNoEnd time (ISO8601, required for external events) (ISO8601 time)
scheduled_start_timeNoStart time (ISO8601) (ISO8601 time)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 safety profile is largely covered. The description does add useful behavior: it discloses that lifecycle transitions are done by writing status values (2 active, 3 completed, 4 cancelled) through a PATCH endpoint. It omits what permissions are required, whether omitted fields are preserved (PATCH partial-update semantics), and that cancellation is a status write rather than a deletion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence followed by the endpoint reference — nothing wasted and easy to scan. The status mapping is slightly redundant with the schema, but the structure is clean.

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

Completeness2/5

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

This is a 14-parameter mutation tool with no output schema, and the description covers only one parameter's values. It says nothing about permission requirements, partial-update behavior, conditional field requirements for external events, or what the response contains — significant gaps for a tool of this complexity.

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?

With 71% schema description coverage across 14 parameters, the schema does most of the work. The description's only parameter-level content is the status code mapping, which the schema already states verbatim, so it adds essentially no new meaning. It could have explained the interactions between status, entity_type (3 external requires scheduled_end_time and entity_metadata.location) and which fields are required for which transition.

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 states a specific verb set ('Edit or start/end/cancel') applied to a clear resource ('an event'), plus the endpoint PATCH /guilds/{guild_id}/scheduled-events/{event_id}. That distinguishes it from the create/delete/get/list siblings, though it never names them or mentions the _exception variant, so differentiation is inferred rather than stated.

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?

Usage is only implied by the verb 'Edit' — an agent can infer this is the mutation tool and not the create/delete/list tools from the name and endpoint. There is no explicit when-to-use guidance, no prerequisites (e.g. MANAGE_EVENTS permission), and no exclusion against modify_guild_scheduled_event_exception, which handles a related but different concept.

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