Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_sticker

Upload a custom Discord server sticker from a PNG, APNG, GIF, or Lottie file (≤512KB) using the first provided file, with a name and emoji tags.

Instructions

Upload a sticker (PNG/APNG/GIF/Lottie ≤512KB). Give the image as files: [{path|url}] (first file is used). [POST /guilds/{guild_id}/stickers]

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>",
      "name": "<name>",
      "tags": "<tags>"
    },
    "name": "create_guild_sticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName
tagsYesRelated emoji name, e.g. "smile"
filesNoFiles to attach (each: path, url or data_base64)
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
descriptionNoDescription

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare that this is a non-read-only, open-world, non-destructive mutation. The description adds useful behavioral constraints beyond annotations: accepted file formats, the 512KB size cap, and that only the first file is used. It does not disclose permission requirements, failure conditions, or rate limits.

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 short and front-loaded: the operation, format/size constraints, file input convention, and endpoint appear in quick succession with no filler. Every sentence contributes operational information.

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?

The description covers the core upload mechanics and schema is fully documented, but it omits context that matters for a guild sticker upload, such as required permissions, guild sticker-slot/boost prerequisites, and response behavior. With annotations and a complete input schema, it is adequate but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all six parameters, and the baseline would be 3. The description adds meaningful semantics beyond the schema by specifying the sticker file formats, the 512KB limit, and the important rule that only the first file in the files array is used.

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

Purpose5/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 ('Upload a sticker') and adds concrete constraints: accepted formats (PNG/APNG/GIF/Lottie) and a 512KB limit. It also provides the underlying endpoint, making the operation distinguishable from sibling tools such as modify_guild_sticker and delete_guild_sticker.

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 does not explain when to use this tool versus alternatives like modify_guild_sticker or create_guild_emoji, nor does it state prerequisites such as guild sticker slots, boost requirements, or permissions. The upload intent is implied by the name and description, but no actual usage guidance is provided.

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