Skip to main content
Glama
scarecr0w12

discord-mcp

list_stickers

Retrieve all custom stickers from a Discord server by providing the server ID. This tool helps users view and manage their server's sticker collection.

Instructions

List all custom stickers in a server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guildIdYesThe ID of the server (guild)

Implementation Reference

  • Registration of the 'list_stickers' MCP tool, including description, input schema (guildId), and complete handler function that lists custom stickers from a Discord guild.
    server.tool(
      'list_stickers',
      'List all custom stickers in a server',
      {
        guildId: z.string().describe('The ID of the server (guild)'),
      },
      async ({ guildId }) => {
        const result = await withErrorHandling(async () => {
          const client = await getDiscordClient();
          const guild = await client.guilds.fetch(guildId);
          const stickers = await guild.stickers.fetch();
    
          return stickers.map((sticker) => ({
            id: sticker.id,
            name: sticker.name,
            description: sticker.description,
            tags: sticker.tags,
            format: sticker.format,
            available: sticker.available,
            guildId: sticker.guildId,
            user: sticker.user ? { id: sticker.user.id, username: sticker.user.username } : null,
            url: sticker.url,
          }));
        });
    
        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)
    Top-level registration call that invokes registerEmojiTools to add the 'list_stickers' tool (among others) to the main MCP server instance.
    registerEmojiTools(server);
  • The handler function executing the 'list_stickers' tool logic: fetches Discord client, retrieves guild stickers, maps to formatted objects, handles errors with withErrorHandling, and returns JSON string.
    async ({ guildId }) => {
      const result = await withErrorHandling(async () => {
        const client = await getDiscordClient();
        const guild = await client.guilds.fetch(guildId);
        const stickers = await guild.stickers.fetch();
    
        return stickers.map((sticker) => ({
          id: sticker.id,
          name: sticker.name,
          description: sticker.description,
          tags: sticker.tags,
          format: sticker.format,
          available: sticker.available,
          guildId: sticker.guildId,
          user: sticker.user ? { id: sticker.user.id, username: sticker.user.username } : null,
          url: sticker.url,
        }));
      });
    
      if (!result.success) {
        return { content: [{ type: 'text', text: result.error }], isError: true };
      }
    
      return { content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }] };
    }
  • Input schema for 'list_stickers' tool using Zod: requires guildId as string.
    {
      guildId: z.string().describe('The ID of the server (guild)'),
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it's a list operation, implying read-only behavior, but doesn't disclose any behavioral traits such as permissions required, rate limits, pagination, or what 'all' entails (e.g., includes default stickers?). For a tool with no annotations, this is a significant gap in transparency.

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 front-loads the core action ('List all custom stickers') and resource ('in a server'). There's no wasted words or redundancy, making it highly concise and well-structured.

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 the tool's low complexity (single parameter, no output schema, no annotations), the description is minimally complete but lacks depth. It states what the tool does but omits behavioral details and usage context, making it adequate but with clear gaps for an agent to rely on.

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 the single parameter 'guildId' documented as 'The ID of the server (guild)'. The description adds no additional parameter semantics beyond this, so it meets the baseline of 3 where 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 verb ('List') and resource ('custom stickers in a server'), specifying it retrieves all custom stickers. However, it doesn't explicitly differentiate from sibling tools like 'list_emojis' or 'get_sticker_info' (if present), though 'list_stickers' is unique among the provided siblings.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing a guild ID), exclusions, or related tools like 'create_sticker' or 'delete_sticker' for context. It's a standalone statement with no usage context.

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