Skip to main content
Glama
cappyeo

discord-mcp

by cappyeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

emojis_modify

Idempotent

Update a Discord emoji's name or role restrictions to manage access. Use when renaming an emoji or limiting it to specific roles, not for changing the image.

Instructions

Purpose: Update a guild emoji's name and/or role restrictions.

When to use:

  • Rename an emoji; restrict to a role tier.

When NOT to use:

  • Replacing the image - Discord does not allow editing emoji bytes; create a new one and delete the old.

Returns: {id, name, animated, roles}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew name (2-32 chars)
rolesNoReplacement role list (empty array = everyone)
emoji_idYesEmoji to modify
guild_idYesGuild owning the emoji
audit_reasonNoReason recorded in audit log (X-Audit-Log-Reason header)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.28.0
    • 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"
-          }
-        ]
-      },
-      "roles": {
-        "items": {
-          "description": "Discord role ID",
-          "pattern": "^\\d{17,20}$",
-          "type": "string"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "id",
-      "name",
-      "animated",
-      "roles"
-    ],
-    "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"
+        ]
+      },
+      "roles": {
+        "items": {
+          "description": "Discord role ID",
+          "pattern": "^\\d{17,20}$",
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "animated",
+      "roles"
+    ],
+    "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"
+  }
+]
  2. First observedv0.22.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint false, destructiveHint false, idempotentHint true). The description adds useful behavioral context beyond annotations: it states the return shape and explicitly notes that emoji bytes cannot be edited, which is a meaningful constraint not captured by annotations.

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 sections (Purpose, When to use, When NOT to use, Returns). Every sentence adds value, and the purpose is front-loaded. It is concise without redundancy.

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?

The description is complete for this tool's complexity. It covers purpose, usage constraints, the return shape, and the key limitation on image replacement. Combined with the schema and annotations, an agent has everything needed to call the tool correctly.

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 description does not add meaning beyond the schema's parameter descriptions. The schema already explains name, roles, guild_id, etc., so the description provides no additional semantic value beyond what the schema offers.

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 clearly states the verb 'Update' and the resource 'guild emoji', and specifies the attributes (name and role restrictions). This distinguishes it from siblings like emojis_create and emojis_delete, which have different verbs and resources.

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. The when-not section explains that image replacement is impossible and directs the agent to create and delete instead, offering clear guidance on alternative actions.

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

Deploy Server

Other Tools