Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Cancel scheduled message

cancel_scheduled_message
Destructive

Cancel a pending scheduled Discord message by ID, deleting its queued text and stopping any repeat. The first call returns a preview and token; repeat with the token to confirm.

Instructions

Cancel a pending scheduled message by its id. The queued text is gone for good, and a repeat stops, so the first call returns a preview and a confirm_token; repeating the call with the token cancels it.

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": {
      "schedule_id": "<schedule_id>"
    },
    "name": "cancel_scheduled_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoGuild (server) name or ID. Omit to use the default guild.
dry_runNo
schedule_idYes
confirm_tokenNoThe token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token
      Added value: +{
+  "description": "The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.",
+  "type": "string"
+}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag destructive=true and readOnly=false, but the description adds substantive behavior the annotations cannot convey: the deletion is irreversible ('the queued text is gone for good'), a second identical call is blocked, and the required preview/confirm_token handshake is spelled out. It omits permission requirements and what the preview actually contains.

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

Conciseness3/5

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

Purpose is front-loaded, which is good, but the second sentence is a run-on whose middle clause ('a repeat stops') is awkward and forces re-reading to grasp the preview/confirm sequence. It could be split into two clean sentences without losing content.

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 destructive mutation with no output schema and only half the parameters documented, the description covers the critical irreversibility and confirm-token flow but leaves dry_run undefined and says nothing about what the preview returns. An agent can call it safely only after inferring the dry_run semantics from the schema name.

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?

Schema coverage is 50%: guild and confirm_token are already documented in the schema, and the description only restates the token flow. The unexplained dry_run flag and the minimal 'by its id' gloss on schedule_id add no meaning 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 ('Cancel a pending scheduled message by its id'), which is clearly distinct from siblings like cancel_event or delete_message. It does not explicitly name an alternative, but the resource noun does the differentiation work.

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?

The use case is implied by the verb and the id requirement, and the description explains the two-step confirm protocol. However, it never says when not to use it or points to list_scheduled_messages for finding an id, and there is no mention of dry_run as an alternative to a real cancel.

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