emojis_modify

Emojis Writes to Discord

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.

MCP call example

{
  "name": "emojis_modify",
  "arguments": {
    "guild_id": "123456789012345678",
    "emoji_id": "123456789012345678",
    "name": "Example name"
  }
}

Input

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 modify
`name`	string	no	min length: `2`; max length: `32`	New name (2-32 chars)
`roles`	array<string>	no		Replacement role list (empty array = everyone)
`audit_reason`	string	no	min length: `1`; max length: `512`	Reason recorded in audit log (X-Audit-Log-Reason header)

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 modify"
    },
    "name": {
      "description": "New name (2-32 chars)",
      "type": "string",
      "minLength": 2,
      "maxLength": 32
    },
    "roles": {
      "description": "Replacement role list (empty array = everyone)",
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\d{17,20}$",
        "description": "Discord role ID"
      }
    },
    "audit_reason": {
      "description": "Reason recorded in audit log (X-Audit-Log-Reason header)",
      "type": "string",
      "minLength": 1,
      "maxLength": 512
    }
  },
  "required": [
    "guild_id",
    "emoji_id"
  ]
}

Returns

{id, name, animated, roles}.

Example structured result

{
  "id": "123456789012345678",
  "name": "Example name",
  "animated": true,
  "roles": [
    "123456789012345678"
  ]
}

Output schema

Field	Type	Required
`id`	string \| null	yes
`name`	string \| null	yes
`animated`	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": {
      "type": [
        "string",
        "null"
      ]
    },
    "animated": {
      "type": "boolean"
    },
    "roles": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\d{17,20}$",
        "description": "Discord role ID"
      }
    }
  },
  "required": [
    "id",
    "name",
    "animated",
    "roles"
  ],
  "additionalProperties": false
}

Annotations

Property	Value
Read-only	no
Destructive	no
Idempotent	yes
Open-world	yes
Confirmation required	no

Access and common errors

The emojis category must be enabled by MCP_CATEGORIES when an allowlist is set.
Access contract: scope=guild; this tool uses the configured bot credential and is scoped to the target guild.
Required permission bits: MANAGE_GUILD_EXPRESSIONS.
Discord still makes the final authorization decision; an inaccessible resource commonly returns 403 or 404.

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

packages/mcp-core/src/tools/emojis/modify.ts