emojis_get
Fetch a single guild emoji by ID.
When to use
Section titled “When to use”- Verify an emoji exists; inspect role-restriction list.
MCP call example
Section titled “MCP call example”{ "name": "emojis_get", "arguments": { "guild_id": "123456789012345678", "emoji_id": "123456789012345678" }}| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
guild_id | string | yes | pattern: ^\d{17,20}$ | Guild owning the emoji |
emoji_id | string | yes | pattern: ^\d{17,20}$ | Emoji to fetch |
Complete input JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "guild_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Guild owning the emoji" }, "emoji_id": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Emoji to fetch" } }, "required": [ "guild_id", "emoji_id" ]}Returns
Section titled “Returns”{id, name, animated, available, roles}.
Example structured result
Section titled “Example structured result”{ "id": "123456789012345678", "name": "Example name", "animated": true, "available": true, "roles": [ "123456789012345678" ]}Output schema
Section titled “Output schema”| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
id | string | null | yes | ||
name | string | null | yes | ||
animated | boolean | yes | ||
available | boolean | yes | ||
roles | array<string> | yes |
Complete output JSON Schema
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "anyOf": [ { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord custom emoji ID" }, { "type": "null" } ] }, "name": { "anyOf": [ { "type": "string" }, { "type": "null" } ] }, "animated": { "type": "boolean" }, "available": { "type": "boolean" }, "roles": { "type": "array", "items": { "type": "string", "pattern": "^\\d{17,20}$", "description": "Discord role ID" } } }, "required": [ "id", "name", "animated", "available", "roles" ], "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
emojiscategory 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/emojis/get.ts