Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_guild_application_command

Destructive

Deletes a guild-specific application command from a Discord server using its application, guild, and command IDs. Use it to remove outdated or unwanted slash commands from a server.

Instructions

Delete Guild Application Command. [DELETE /applications/{application_id}/guilds/{guild_id}/commands/{command_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": {
      "application_id": "<application_id>",
      "guild_id": "<guild_id>",
      "command_id": "<command_id>"
    },
    "name": "delete_guild_application_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
command_idYesApplication command ID
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the agent knows this is an irreversible mutation against an external service. The description adds the HTTP verb and route, which confirms scope, but says nothing about required permissions (e.g., needing to own the application/bot), whether deletion cascades or affects registered commands in servers, or what a successful response looks like.

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?

Two compact, front-loaded elements: the action phrase then the route. Nothing is padded, though the bracketed endpoint is arguably redundant with the parameters and reads as mechanical rather than explanatory.

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?

All three required parameters are documented in the schema and there is no output schema to explain, so the basics are covered. For a destructive, open-world operation with zero annotation-independent detail on permissions or side effects, the description is adequate but leaves real gaps.

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 description coverage is 100% — guild_id, command_id, and application_id each carry a description in the schema. The endpoint template mirrors those parameters but adds no semantics beyond them, so the baseline 3 applies.

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+resource ('Delete Guild Application Command') and reinforces scope with the raw endpoint [DELETE /applications/{application_id}/guilds/{guild_id}/commands/{command_id}], so an agent can tell this targets a guild-scoped command rather than a global one. It stops short of explicitly naming delete_global_application_command as the counterpart, so differentiation relies on the word 'Guild' and the path.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as delete_global_application_command or bulk_modify_guild_application_commands. The agent must infer selection purely from the tool name and endpoint path.

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