discord-mcp

app_emojis_modify

Idempotent

Rename an application emoji to update its public-facing name. Omit application_id to modify an emoji owned by the authenticated bot application.

Instructions

Purpose: Rename an application emoji.

When to use:

Update the public-facing name of an app emoji.
Omit application_id to modify an emoji owned by the authenticated bot application.

When NOT to use:

Replacing image bytes - Discord does not allow editing emoji bytes; create and verify a replacement with app_emojis_create, then remove the old one with confirmation via app_emojis_delete.

Returns: {id, name, animated}.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	New emoji name (2-32 ASCII letters, digits, or underscores)
`emoji_id`	Yes	Emoji to modify
`application_id`	No	Application owning the emoji (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": {
-      "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"
-  },
-  {
-    "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": {
+      "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"
+  },
+  {
+    "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"
+  }
+]

Changed4 schema fields changedv0.26.0Sep 1, 2026

changedInput schema / properties / application_id / description

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

changedInput schema / properties / name / description

Previous value: -"New emoji name (2-32 chars)"New value: +"New emoji name (2-32 ASCII letters, digits, or underscores)"

addedInput schema / properties / name / pattern
```
Added value: +"^[A-Za-z0-9_]{2,32}$"
```

changedInput schema / required

Previous value: -[
-  "application_id",
-  "emoji_id"
-]New value: +[
+  "emoji_id",
+  "name"
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare non-read-only, idempotent, and non-destructive behavior, so the description's safety burden is reduced. The description adds useful limitations—no byte editing, return shape—but does not add deeper context such as explicit permission requirements or error behavior. It is accurate and consistent with annotations, but not rich.

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 clearly structured with bold section headers, short purpose, focused usage rules, and a compact return hint. Every section adds value, and the operative meaning is front-loaded.

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

Completeness4/5

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

The description covers purpose, when to use, when not to use, alternatives, and return shape, which is enough for a simple rename tool with annotations and an output schema present. I minor gap is the lack of explicit mentioning permission/authorization requirements for modifying an app emoji, but this is not critical for a simple rename operation.

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 schema already has 100% description coverage for all three parameters, including the omission behavior for application_id. The description mostly restates this and doesn't meaningfully enrich what an agent would already understand from the schema.

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 opens with a concrete statement — 'Rename an application emoji' — and distinguishes this tool from image-replacement flows by explicitly saying Discord does not allow editing emoji bytes. It also differentiates the 'app emoji' scope from the many sibling emoji tools without ambiguity.

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?

There is a dedicated 'When to use' section and a 'When NOT to use' section that points to app_emojis_create and app_emojis_delete for image replacement. This gives the agent a clear decision rule and names the exact alternative workflow.

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

Deploy Server