Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create sticker

create_sticker

Upload a custom Discord sticker from an image URL in PNG, APNG, or GIF format at 320x320 px and up to 512 KB so AI agents can add server stickers.

Instructions

Upload a custom sticker from an image URL. Discord requires png, apng, or gif at 320x320 pixels and up to 512 KB. Servers start with five sticker slots; boosts add more.

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": {
      "name": "<name>",
      "tags": "<tags>",
      "image_url": "<image_url>"
    },
    "name": "create_sticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
tagsYesComma separated keywords, or one emoji name for autocomplete.
guildNoGuild (server) name or ID. Omit to use the default guild.
image_urlYes
descriptionNoEmpty or 2-100 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds substantive behavioral context — required image formats, 320x320 dimensions, 512 KB cap, and the server slot/boost limitation. It does not cover permission requirements or what happens when slots are exhausted, but the added constraints go well beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and followed by the constraints that matter for a successful call. The slot/boost sentence is slightly tangential but still relevant precondition context, so little is wasted.

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

Completeness4/5

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

For a mutation tool with no output schema, the description covers the essential creation constraints and the capacity limitation, which is enough for an agent to attempt the call correctly. It stops short of stating required permissions or the failure mode when slots are full, a minor gap given the annotations already mark it as a non-destructive write.

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 60%, and the description compensates by specifying the accepted image formats, dimensions, and file size for image_url, which the schema alone (format: uri) does not convey. It adds no meaning for name, tags, guild, or description, leaving part of the parameter set to the schema.

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?

States a specific verb and resource ('Upload a custom sticker from an image URL'), which is unambiguous and clearly distinguishable from sibling tools like delete_sticker, update_sticker, and create_emoji.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when the tool applies (uploading a sticker) but gives no explicit when-to-use/when-not guidance and does not name alternatives such as create_emoji for emoji uploads. The slot-limit sentence hints at a precondition (available slots) without stating what to do when none remain.

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