Skip to main content
Glama
scarecr0w12

discord-mcp

delete_sticker

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

Instructions

Delete a custom sticker from a server

Input Schema

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

Implementation Reference

  • The handler function that executes the delete_sticker tool: fetches the Discord guild and sticker, deletes the sticker with optional reason, handles errors with withErrorHandling, and returns JSON-formatted response.
    async ({ guildId, stickerId, reason }) => {
      const result = await withErrorHandling(async () => {
        const client = await getDiscordClient();
        const guild = await client.guilds.fetch(guildId);
        const sticker = await guild.stickers.fetch(stickerId);
        const stickerName = sticker.name;
    
        await sticker.delete(reason);
    
        return { stickerId, stickerName, message: 'Sticker 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) }] };
    }
  • Zod schema for input parameters: required guildId and stickerId, optional reason.
    {
      guildId: z.string().describe('The ID of the server (guild)'),
      stickerId: z.string().describe('The ID of the sticker to delete'),
      reason: z.string().optional().describe('Reason for deleting the sticker'),
    },
  • Registers the 'delete_sticker' tool on the MCP server, including name, description, input schema, and handler function.
    server.tool(
      'delete_sticker',
      'Delete a custom sticker from a server',
      {
        guildId: z.string().describe('The ID of the server (guild)'),
        stickerId: z.string().describe('The ID of the sticker to delete'),
        reason: z.string().optional().describe('Reason for deleting the sticker'),
      },
      async ({ guildId, stickerId, reason }) => {
        const result = await withErrorHandling(async () => {
          const client = await getDiscordClient();
          const guild = await client.guilds.fetch(guildId);
          const sticker = await guild.stickers.fetch(stickerId);
          const stickerName = sticker.name;
    
          await sticker.delete(reason);
    
          return { stickerId, stickerName, message: 'Sticker 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)
    Calls registerEmojiTools which includes the registration of delete_sticker among other emoji/sticker tools.
    registerEmojiTools(server);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive operation, the description doesn't mention important behavioral aspects like required permissions, whether the deletion is permanent or reversible, rate limits, or what happens after deletion. For a destructive operation with zero annotation coverage, this is inadequate.

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, efficient sentence that gets straight to the point with no wasted words. It's appropriately sized for a simple operation and front-loads the essential information.

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 operation with no annotations and no output schema, the description is insufficient. It doesn't address important contextual information like required permissions, consequences of the operation, error conditions, or what the tool returns. Given the complexity of a deletion operation in a Discord-like system, more completeness is needed.

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 input schema has 100% description coverage, with all three parameters clearly documented in the schema itself. The description doesn't add any additional parameter information beyond what's already in the schema descriptions, so it meets the baseline of 3 for high schema coverage.

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 sticker from a server'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other deletion tools in the sibling list (like delete_emoji, delete_message, delete_role), which would require 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 provides no guidance on when to use this tool versus alternatives. There are many other deletion tools in the sibling list (delete_emoji, delete_message, delete_role, etc.), but the description doesn't explain what makes this one different or when it's appropriate versus other deletion operations.

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