discord-mcp

app_emojis_list

Read-onlyIdempotent

List custom emojis registered to a Discord application, usable across any guild. Provide an application ID or omit it to use the authenticated bot and retrieve emoji IDs, names, animated flags, and count.

Instructions

Purpose: List custom emojis registered against the application (per-app, not per-guild; up to 2,000).

When to use:

Inspect app-level emojis usable from any guild the bot is in.
Omit application_id to inspect the application belonging to the authenticated bot.

When NOT to use:

Guild-scoped emojis → use emojis_list_guild.

Returns: {emojis:[{id, name, animated}], count}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`application_id`	No	Application owning the emojis (omit to use the authenticated bot application)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.28.0Sep 15, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "count": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      },
-      "emojis": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "animated": {
-              "type": "boolean"
-            },
-            "id": {
-              "anyOf": [
-                {
-                  "description": "Discord custom emoji ID",
-                  "pattern": "^\\d{17,20}$",
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "name": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "required": [
-            "id",
-            "name",
-            "animated"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "emojis",
-      "count"
-    ],
-    "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": {
+      "count": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "emojis": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "animated": {
+              "type": "boolean"
+            },
+            "id": {
+              "anyOf": [
+                {
+                  "description": "Discord custom emoji ID",
+                  "pattern": "^\\d{17,20}$",
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "animated"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "emojis",
+      "count"
+    ],
+    "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"
+  }
+]

Changed2 schema fields changedv0.26.0Sep 1, 2026

changedInput schema / properties / application_id / description

Previous value: -"Application owning the emojis"New value: +"Application owning the emojis (omit to use the authenticated bot application)"

removedInput schema / required

Removed value: -[
-  "application_id"
-]

First observedv0.22.0Aug 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds meaningful context beyond the annotations: the app-level vs guild-level scoping and the hard upper bound of 2,000 emojis. This gives the agent useful expectations without conflicting with structured metadata.

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 well-structured with clear headings: Purpose, When to use, When NOT to use, and Returns. Each section is short, front-loaded, and contains only necessary information, making it easy for an agent to parse and act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with one optional parameter, full schema coverage, a present output schema, and explicit sibling differentiation, the description is complete. It covers scope, constraints, usage, and expected return shape, so no critical information is missing for correct invocation.

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

Parameters3/5

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

Schema coverage is 100%, and the single parameter already has a clear description including the omission behavior. The tool description repeats the same 'omit application_id' guidance, so it adds no new semantic value beyond the schema. Baseline 3 applies since the schema carries the parameter documentation adequately.

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 states a specific verb ('List') and resource ('custom emojis registered against the application'), and explicitly distinguishes from guild-scoped emojis by clarifying 'per-app, not per-guild'. This makes the tool's purpose unambiguous and differentiates it from emojis_list_guild.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'When to use' section provides concrete inspection scenarios, and the 'When NOT to use' section explicitly routes to the sibling tool emojis_list_guild. It also explains the optional application_id behavior, leaving no ambiguity about how to invoke the tool correctly.

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

Deploy Server