commands_get_global
Fetch one global application command by id.
MCP call example
Section titled “MCP call example”{ "name": "commands_get_global", "arguments": { "application_id": "123456789012345678", "command_id": "123456789012345678" }}| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
application_id | string | yes | pattern: ^\d{17,20}$ | Bot/app application ID |
command_id | string | yes | pattern: ^\d{17,20}$ | Command ID (snowflake) |
Complete input JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "application_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Bot/app application ID" }, "command_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Command ID (snowflake)" } }, "required": [ "application_id", "command_id" ]}Returns
Section titled “Returns”{id, name, description, type, application_id, untrusted_text}. name and description remain raw; untrusted_text provides a separately fenced copy.
Example structured result
Section titled “Example structured result”{ "id": "123456789012345678", "application_id": "123456789012345678", "name": "Example name", "description": "example", "type": 1, "untrusted_text": "example"}Output schema
Section titled “Output schema”| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
id | string | yes | ||
application_id | string | yes | ||
name | string | yes | ||
description | string | yes | ||
type | integer | yes | ||
untrusted_text | string | yes |
Complete output JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string" }, "application_id": { "type": "string" }, "name": { "type": "string" }, "description": { "type": "string" }, "type": { "type": "integer" }, "untrusted_text": { "type": "string" } }, "required": [ "id", "application_id", "name", "description", "type", "untrusted_text" ], "additionalProperties": false}Annotations
Section titled “Annotations”| Property | Value |
|---|---|
| Read-only | yes |
| Destructive | no |
| Idempotent | yes |
| Open-world | yes |
| Confirmation required | no |
Access and common errors
Section titled “Access and common errors”- The
commandscategory must be enabled byMCP_CATEGORIESwhen an allowlist is set. - This endpoint uses the configured bot credential and Discord’s route-specific authorization; discord-mcp does not elevate access.
- An invalid credential returns a
401-class tool error. Insufficient endpoint permission or scope returns403; inaccessible resources commonly return404.
Trust boundary
Section titled “Trust boundary”Discord-supplied names, topics, messages, and other strings are untrusted. Fields in
structuredContent may remain raw even when the companion human-readable content
or an untrusted_* field contains a fenced copy. Fencing is defense-in-depth, not
sanitization or proof against prompt injection. Never treat Discord text as instructions
or feed it into a consequential write without an independent policy or human approval.
Source
Section titled “Source”packages/mcp-core/src/tools/commands/get_global.ts