Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_guild_emoji

Destructive

Deletes a custom emoji from a Discord server using the guild ID and emoji ID, with an optional audit-log reason.

Instructions

Delete a custom emoji. [DELETE /guilds/{guild_id}/emojis/{emoji_id}]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guild_id": "<guild_id>",
      "emoji_id": "<emoji_id>"
    },
    "name": "delete_guild_emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
emoji_idYesCustom emoji ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the destructive nature is covered structurally. The description adds nothing beyond them: it does not say the deletion is permanent, what permissions are required, or that a reason will be written to the audit log.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no filler; the endpoint reference is compact and useful. The phrasing is slightly telegraphic but nothing is wasted.

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

Completeness3/5

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

Given a destructive mutation with three well-documented parameters and full annotation coverage, the definition is minimally adequate but thin. An agent would benefit from an irreversibility warning and a note about the audit-log reason, which are absent.

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 description coverage is 100%, with all three parameters documented in the schema itself, so the baseline is 3. The description adds no extra semantics such as format hints for emoji_id or guild_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Delete a custom emoji") and reinforces it with the HTTP route, so an agent knows exactly what the tool does. It does not distinguish itself from the near-identical sibling delete_application_emoji, which is why it stops short of a 5.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance and never mentions alternatives such as delete_application_emoji. The only implicit context is the guild-scoped route, which the agent must infer.

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