Skip to main content
Glama
scarecr0w12

discord-mcp

create_sticker

Create custom stickers for Discord servers by providing an image URL, name, description, and tags to enhance server customization and communication.

Instructions

Create a custom sticker in a server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guildIdYesThe ID of the server (guild)
nameYesName for the sticker (2-30 characters)
descriptionYesDescription of the sticker
tagsYesAutocomplete/suggestion tags for the sticker
imageUrlYesURL of the image (PNG, APNG, GIF, or Lottie JSON)
reasonNoReason for creating the sticker

Implementation Reference

  • The handler function that performs the core logic of creating a custom sticker in a Discord server using the guild.stickers.create method, wrapped in error handling, and returns a formatted JSON response.
    async ({ guildId, name, description, tags, imageUrl, reason }) => {
      const result = await withErrorHandling(async () => {
        const client = await getDiscordClient();
        const guild = await client.guilds.fetch(guildId);
    
        const sticker = await guild.stickers.create({
          file: imageUrl,
          name,
          description,
          tags,
          reason,
        });
    
        return {
          id: sticker.id,
          name: sticker.name,
          description: sticker.description,
          tags: sticker.tags,
          url: sticker.url,
          message: 'Sticker created 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 validating the input parameters for the create_sticker tool.
    {
      guildId: z.string().describe('The ID of the server (guild)'),
      name: z.string().describe('Name for the sticker (2-30 characters)'),
      description: z.string().describe('Description of the sticker'),
      tags: z.string().describe('Autocomplete/suggestion tags for the sticker'),
      imageUrl: z.string().describe('URL of the image (PNG, APNG, GIF, or Lottie JSON)'),
      reason: z.string().optional().describe('Reason for creating the sticker'),
    },
  • Registers the create_sticker tool on the MCP server using server.tool(), including name, description, input schema, and handler function.
      'create_sticker',
      'Create a custom sticker in a server',
      {
        guildId: z.string().describe('The ID of the server (guild)'),
        name: z.string().describe('Name for the sticker (2-30 characters)'),
        description: z.string().describe('Description of the sticker'),
        tags: z.string().describe('Autocomplete/suggestion tags for the sticker'),
        imageUrl: z.string().describe('URL of the image (PNG, APNG, GIF, or Lottie JSON)'),
        reason: z.string().optional().describe('Reason for creating the sticker'),
      },
      async ({ guildId, name, description, tags, imageUrl, reason }) => {
        const result = await withErrorHandling(async () => {
          const client = await getDiscordClient();
          const guild = await client.guilds.fetch(guildId);
    
          const sticker = await guild.stickers.create({
            file: imageUrl,
            name,
            description,
            tags,
            reason,
          });
    
          return {
            id: sticker.id,
            name: sticker.name,
            description: sticker.description,
            tags: sticker.tags,
            url: sticker.url,
            message: 'Sticker created 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)
    Invokes registerEmojiTools to register the emoji and sticker tools, including create_sticker, on the main MCP server instance.
    registerEmojiTools(server);
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. It states the action ('Create') which implies a write/mutation operation, but doesn't disclose any behavioral traits like required permissions, rate limits, whether the operation is idempotent, what happens on failure, or what the response contains. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 states the core purpose without unnecessary words. It's appropriately sized for a tool with good schema documentation and gets straight to the point with zero wasted text.

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 mutation tool with 6 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address behavioral aspects like permissions needed, error conditions, or what the tool returns. While the schema covers parameters well, the description should provide more context about the operation's behavior and constraints given the lack of annotations and output schema.

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 6 parameters thoroughly with descriptions of each field. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters, provide examples, or clarify edge cases. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 ('Create') and resource ('custom sticker in a server'), making the purpose immediately understandable. It distinguishes this tool from other creation tools like create_emoji or create_channel by specifying the sticker resource type. However, it doesn't explicitly differentiate from modify_sticker, which handles updates rather than initial creation.

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. It doesn't mention prerequisites (like required permissions), when not to use it, or how it differs from sibling tools like modify_sticker or create_emoji. The agent must infer usage context solely from the tool name and schema.

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