discord-mcp

commands_create_global

Idempotent

Create or update a global Discord application command. Posting the same name and type updates the existing command, with changes propagating within an hour.

Instructions

Purpose: Create or upsert a global application command. Global commands propagate within ~1 hour.

Body: standard command shape - name is required. description is required for CHAT_INPUT (type=1) but optional for USER (2) / MESSAGE (3) commands.

Idempotent: posting the same name+type updates the existing command (Discord upsert semantics).

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

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`nsfw`	No
`type`	No
`handler`	No
`options`	No
`contexts`	No
`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

B3.2/5.0

Behavior4/5

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

Adds meaningful detail beyond annotations: idempotent upsert semantics ('posting the same name+type updates'), a ~1 hour propagation delay, and that description is required for CHAT_INPUT but optional for USER/MESSAGE. These complement the idempotentHint and readOnlyHint=false annotations. Also provides a return shape. Lacks mention of side effects like overwriting, but upsert is explicit.

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?

Well-structured with bold headers, front-loaded purpose, and clear separation of concerns. Each sentence earns its place—purpose, body constraints, idempotency, and return. No fluff or redundancy.

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?

Incomplete for a complex 14-parameter tool. It covers only the basics (name, description, type) and idempotency, but omits the options structure, choices, permission fields, and other advanced parameters. While an output schema exists, the input semantics for most parameters are missing, making it insufficient for fully informed usage.

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 7% (2 of 14 parameters). The description clarifies name and description requirements and the type-dependent description constraint, but leaves options, choices, contexts, permissions, and other fields unexplained. The phrase 'standard command shape' is vague and does not compensate for the low schema coverage.

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?

States 'Create or upsert a global application command' with a specific verb and resource. The term 'global' clearly distinguishes from guild-scoped commands like commands_create_guild, though it doesn't explicitly name alternatives. It's clear but not as explicit as naming a sibling.

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?

No explicit guidance on when to use this tool versus alternatives such as commands_create_guild or commands_modify_global. The propagation delay is a property, not a usage direction. No when/when-not or alternative recommendations are given.

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

Deploy Server