discord-mcp

commands_modify_guild

Idempotent

Modify an existing Discord command in a guild by updating any fields like name, description, options, or permissions. Pass application, guild, and command IDs to apply changes.

Instructions

Purpose: Edit a guild-scoped command. All command-body fields are optional.

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

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`nsfw`	No
`type`	No
`handler`	No
`options`	No
`contexts`	No
`guild_id`	Yes	Guild scope
`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 cover read-only, destructive, and idempotent behavior. The description adds useful behavioral context: all command-body fields are optional, implying a partial patch rather than a full replacement, and it discloses the response shape. No contradiction with 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?

Two purposeful, front-loaded sections: Purpose followed by Returns. Every sentence adds value, with no filler or repetition of schema information.

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?

The description provides the core essentials: scope, optionality, and return shape, while annotations cover safety behavior and the output schema covers return structure. However, given the tool's complexity and low parameter documentation coverage, the description remains minimal and an agent would still need external knowledge to use several command-body fields correctly.

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 19%, so the description must compensate for the 13 undocumented command-body parameters. It only says 'all command-body fields are optional,' which is already inferable from the schema's required list. It does not clarify domain-specific fields like handler, contexts, integration_types, or default_permission.

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 starts with a specific verb-resource pair: 'Edit a guild-scoped command.' This clearly distinguishes it from create/delete/get command tools and from global-scoped command tools via the 'guild-scoped' qualifier.

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 phrase 'guild-scoped command' clearly communicates the intended scope, letting an agent choose this over commands_modify_global. However, it does not explicitly name alternatives or provide when-not-to-use guidance, so it stops short of a 5.

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

Deploy Server