Skip to main content
Glama
scarecr0w12

discord-mcp

by scarecr0w12
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

delete_emoji

Remove custom emojis from Discord servers by specifying the server and emoji IDs. This tool helps manage server content by deleting unwanted or outdated custom emojis.

Instructions

Delete a custom emoji from a server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guildIdYesThe ID of the server (guild)
emojiIdYesThe ID of the emoji to delete
reasonNoReason for deleting the emoji

Implementation Reference

  • src/tools/emoji-tools.ts:84-109 (registration)
    Registration and implementation of the 'delete_emoji' MCP tool, including input schema, handler logic that fetches the Discord guild and emoji then deletes it with optional reason, and error handling with response formatting.
    server.tool(
  'delete_emoji',
  'Delete a custom emoji from a server',
  {
    guildId: z.string().describe('The ID of the server (guild)'),
    emojiId: z.string().describe('The ID of the emoji to delete'),
    reason: z.string().optional().describe('Reason for deleting the emoji'),
  },
  async ({ guildId, emojiId, reason }) => {
    const result = await withErrorHandling(async () => {
      const client = await getDiscordClient();
      const guild = await client.guilds.fetch(guildId);
      const emoji = await guild.emojis.fetch(emojiId);
      const emojiName = emoji.name;

      await emoji.delete(reason);

      return { emojiId, emojiName, message: 'Emoji deleted successfully' };
    });

    if (!result.success) {
      return { content: [{ type: 'text', text: result.error }], isError: true };
    }

    return { content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }] };
  }
  • src/index.ts:60-60 (registration)
    High-level registration call for all emoji tools (including delete_emoji) on the MCP server instance.
    registerEmojiTools(server);
  • src/tools/emoji-tools.ts:87-90 (schema)
    Zod input schema validation for the delete_emoji tool parameters.
    {
  guildId: z.string().describe('The ID of the server (guild)'),
  emojiId: z.string().describe('The ID of the emoji to delete'),
  reason: z.string().optional().describe('Reason for deleting the emoji'),

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive operation, it doesn't specify whether this is permanent, reversible, requires specific permissions, or has rate limits. The description lacks critical behavioral context for a destructive operation.

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 a single, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable without unnecessary elaboration.

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

Completeness2/5

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

For a destructive tool with no annotations and no output schema, the description is insufficient. It doesn't address critical context like permissions needed, whether deletion is permanent, what happens to messages using the emoji, or what the response contains. The 100% schema coverage helps with parameters but doesn't compensate for missing behavioral context.

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%, so the schema already documents all three parameters (guildId, emojiId, reason). The description doesn't add any meaningful parameter semantics beyond what's in the schema, such as format requirements or relationship between parameters.

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 clearly states the action ('Delete') and resource ('a custom emoji from a server'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'delete_channel' or 'delete_message', but the specificity of 'emoji' provides inherent distinction.

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 provides no guidance on when to use this tool versus alternatives like 'modify_emoji' or other deletion tools. There's no mention of prerequisites, permissions required, or contextual constraints for emoji deletion.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scarecr0w12/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server