discord-mcp

emojis_list_guild

Read-onlyIdempotent

Lists all custom emojis in a Discord guild, returning their IDs, names, and availability for use in reactions. Use it to inventory emoji options.

Instructions

Purpose: List all custom emojis defined in a guild.

When to use:

Inventory custom emoji; pick one for a reaction or response.

When NOT to use:

Application-scoped emojis → use app_emojis_list.

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`guild_id`	Yes	Guild to inspect

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"
-            },
-            "available": {
-              "type": "boolean"
-            },
-            "id": {
-              "anyOf": [
-                {
-                  "description": "Discord custom emoji ID",
-                  "pattern": "^\\d{17,20}$",
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "name": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "roles": {
-              "items": {
-                "description": "Discord role ID",
-                "pattern": "^\\d{17,20}$",
-                "type": "string"
-              },
-              "type": "array"
-            }
-          },
-          "required": [
-            "id",
-            "name",
-            "animated",
-            "available",
-            "roles"
-          ],
-          "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"
+            },
+            "available": {
+              "type": "boolean"
+            },
+            "id": {
+              "anyOf": [
+                {
+                  "description": "Discord custom emoji ID",
+                  "pattern": "^\\d{17,20}$",
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "roles": {
+              "items": {
+                "description": "Discord role ID",
+                "pattern": "^\\d{17,20}$",
+                "type": "string"
+              },
+              "type": "array"
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "animated",
+            "available",
+            "roles"
+          ],
+          "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"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile. The description adds the return structure ('Returns: {emojis:...}'), but since an output schema exists, this is redundant. It doesn't mention permissions, pagination, or edge cases, so the added value over annotations is minimal. A 3 is appropriate.

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 bold section headers, immediately states the purpose, and contains only essential information. It is front-loaded and every sentence earns its place—no fluff or repetition.

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 parameter, an output schema, and comprehensive annotations, the description covers purpose, usage guidelines, alternatives, and return format. Nothing an agent needs to call it correctly is missing.

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?

The input schema has 100% coverage for the single parameter guild_id with a clear description ('Guild to inspect'). The tool description adds no additional meaning beyond the schema. This matches the baseline 3 for complete schema coverage.

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 clear, specific verb and resource: 'List all custom emojis defined in a guild.' It also distinguishes from app_emojis_list by explicitly mentioning the alternative, making the tool's scope unambiguous. This exceeds the minimum and clearly differentiates from siblings.

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 description provides explicit 'When to use' and 'When NOT to use' sections, including a specific alternative tool (app_emojis_list) for application-scoped emojis. This gives an agent direct routing guidance with no ambiguity.

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

Deploy Server