discord-mcp

commands_modify_global

Idempotent

Update a global Discord application command by passing only the fields to change, including name, description, options, or permissions, and receive the updated command details.

Instructions

Purpose: Edit a global application command. All command-body fields are optional - pass only what changes.

Returns: updated {id, name, description, type, application_id}.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`nsfw`	No
`type`	No
`handler`	No
`options`	No
`contexts`	No
`command_id`	Yes	Command ID to modify
`description`	No
`dm_permission`	No
`application_id`	Yes	Bot/app application ID
`integration_types`	No
`default_permission`	No
`name_localizations`	No
`description_localizations`	No
`default_member_permissions`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 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 / default_permission / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / default_permission / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

removedInput schema / properties / dm_permission / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / dm_permission / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "application_id": {
-        "type": "string"
-      },
-      "description": {
-        "type": "string"
-      },
-      "guild_id": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "id": {
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "type": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "id",
-      "name",
-      "type"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "application_id": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "guild_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "type": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "type"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already signal mutation and idempotency, so the description adds value by disclosing partial-update semantics: 'All command-body fields are optional - pass only what changes.' It also states what the response returns, giving useful behavioral context beyond the raw annotations.

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 compact and front-loaded: the purpose appears first, the partial-update behavior is stated next, and the return shape is provided. Both sentences earn their place with no redundancy.

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 complex tool with 15 parameters and low schema coverage, the description is thin. It covers purpose, scoping, edit semantics, and return value, but it does not explain the meaning of many parameters or provide guidance on when to choose this tool over related command tools. The output schema presumably covers return details, but the overall description leaves notable gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13% with 15 parameters, and the description does not compensate. The only parameter-related guidance is the generic statement that command-body fields are optional; it adds no meaning for ambiguous fields like nsfw, handler, contexts, or integration_types. The two required IDs are self-explanatory in the schema, but most parameters remain semantically unexplained.

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 uses a specific verb-resource pair: 'Edit a global application command', and the word 'global' clearly distinguishes it from sibling guild-scoped command tools like commands_modify_guild. The purpose is immediately identifiable without needing to inspect the schema.

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 clearly contextualizes usage to global application commands, implying it should not be used for guild commands. However, it does not explicitly name alternatives such as commands_modify_guild or state when to prefer create versus modify, so there is no explicit when-not guidance.

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

Deploy Server