Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_create_emoji

Upload a custom emoji to a Discord server from an image URL or data URI, with optional role restrictions. Requires Manage Expressions permission.

Instructions

Upload a custom emoji from an image URL or data URI. Requires Manage Expressions.

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": {
      "guildId": "<guildId>",
      "name": "<name>",
      "url": "<url>"
    },
    "name": "discord_create_emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL or data: URI of a PNG/JPG/GIF image
nameYes
rolesNoRole ids allowed to use the emoji; empty means everyone
reasonNo
guildIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the permission gate, which is genuinely useful, but says nothing about what happens on success (new emoji id), whether the operation is reversible, rate limits, size/dimension limits on the uploaded image, or that name collisions fail.

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?

Two tight sentences with the core action and accepted inputs front-loaded and the permission requirement trailing as a precondition. No filler or redundancy.

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?

This is a mutation tool with no annotations and no output schema, so the description must compensate for both, and it does not. Missing are mutation effects, image constraints (size, format limits), and any indication of what the call returns, which an agent needs before invoking it.

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

Parameters2/5

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

Schema coverage is 60% and the description only restates the url parameter's accepted formats, which the schema already documents verbatim. It adds no meaning for name constraints, roles, reason, or guildId, leaving the undocumented parameters unimproved by the description.

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 states a specific verb and resource ('Upload a custom emoji') plus the accepted input forms (image URL or data URI), which clearly distinguishes it from discord_delete_emoji and other create_* siblings. It stops short of explicitly naming a contrasting sibling, so it lands at 4 rather than 5.

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?

'Requires Manage Expressions' gives a concrete prerequisite, which is real usage guidance. However, there is no statement of when to prefer this over alternatives, no mention of guild emoji slot limits or file-size constraints that would determine whether the call can succeed, and no exclusions.

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