discord-mcp

commands_bulk_overwrite_global

DestructiveIdempotent

Replace the entire global Discord command registry atomically. Use to re-sync commands from a source of truth during CI deploys; an empty array deletes all commands.

Instructions

Purpose: Atomically REPLACE the entire global command registry. Any commands not in commands are deleted.

When to use:

CI deploy: re-sync the canonical command list from source-of-truth.

Caution: this is a wholesale replace - call commands_list_global first to confirm scope. An EMPTY array deletes every global command.

Security: gated by ConfirmRequired. Pass __confirm:true AND set MCP_DRY_RUN=false to actually apply the replace.

Returns: {commands:[{id, name, type}], count}.

Input Schema

TableJSON Schema

Name	Required	Description
`commands`	Yes	Full set of commands to register globally (REPLACES the existing registry; an empty array deletes every command).
`__confirm`	No	Set true to authorize this destructive operation. Also requires the server to run with MCP_DRY_RUN=false; otherwise a DRY_RUN_PREVIEW is returned.
`application_id`	Yes	Bot/app application ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.28.0Sep 15, 2026
- removedInput schema / $defs / __schema0 / properties / choices / items / properties / value / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / $defs / __schema0 / properties / choices / items / properties / value / type
```
Added value: +[
+  "string",
+  "number"
+]
```
- removedInput schema / properties / commands / items / properties / default_permission / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / commands / items / properties / default_permission / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedInput schema / properties / commands / items / properties / dm_permission / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / commands / items / properties / dm_permission / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
First observedv0.22.0Aug 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing that the operation is atomic, that an empty array deletes every global command, that the operation is gated by ConfirmRequired, and that MCP_DRY_RUN=false is required to actually apply changes. This is valuable behavioral context beyond the destructiveHint=true annotation.

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?

The description is well-structured with clear sections: purpose, when to use, caution, security, and returns. It is front-loaded with the most important information and every sentence serves a purpose without unnecessary filler.

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

Completeness5/5

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

For a destructive, confirm-gated bulk operation, the description covers purpose, usage context, safety precautions, security requirements, and return shape. Combined with the full schema and annotations, an agent has everything needed to invoke this tool correctly.

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?

The input schema already provides descriptions for all three parameters, including the meaning of `commands` and `__confirm`. The description adds useful emphasis around the empty-array behavior and the confirm/dry-run gate, but does not substantially expand the semantics of `application_id` beyond what the schema states.

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 states a specific verb ('REPLACE') and resource ('the entire global command registry'), and clarifies the key behavior: commands not in the `commands` array are deleted. This clearly distinguishes it from related tools like commands_create_global, commands_modify_global, and commands_bulk_overwrite_guild.

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

Usage Guidelines4/5

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

The description explicitly identifies the primary use case ('CI deploy: re-sync the canonical command list from source-of-truth') and gives a practical caution to call commands_list_global first to confirm scope. It does not explicitly mention when not to use it or name an alternative for guild-scoped overwrites, but the context is clear enough for correct selection.

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

Deploy Server