Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_global_application_command

Destructive

Deletes a global Discord application command using its app and command IDs, removing the command from the application's global command list.

Instructions

Delete Global Application Command. [DELETE /applications/{application_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>",
      "command_id": "<command_id>"
    },
    "name": "delete_global_application_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
command_idYesApplication command ID
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds no behavioral context of its own — nothing about irreversibility, whether the deletion propagates to command registrations across guilds, or any error conditions.

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?

It is short and front-loaded, which is good, but the bracketed endpoint adds no decision-relevant information and the remaining space is wasted on name repetition rather than on any of the missing guidance.

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?

For a destructive, open-world mutation with no output schema, an agent needs to know that the effect is permanent and that it applies to the global command registry rather than a single guild. None of that is present, so the definition is thin relative to the risk of the operation.

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% with both required parameters documented in the schema, so the baseline of 3 applies. The description contributes no additional meaning about parameter format or identifier sourcing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name verbatim ('Delete Global Application Command') and appends the HTTP route, so the verb+resource are unambiguous but nothing is added beyond the identifier. It never contrasts itself with the closely named sibling delete_guild_application_command, leaving the global-vs-guild scope distinction to be inferred from the name alone.

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 guidance on when to use this instead of delete_guild_application_command or the bulk operations, and no stated prerequisites such as ownership or permissions. The only context offered is the REST endpoint template.

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