Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_emoji

Upload a custom emoji to a Discord server from a local file path, URL, or data URI, with optional role restrictions and audit log reason.

Instructions

Upload a custom emoji (image ≤256KB: path, URL or data URI). [POST /guilds/{guild_id}/emojis]

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>",
      "image": "<image>"
    },
    "name": "create_guild_emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName
imageYesImage: local file path, http(s) URL or data: URI
rolesNoRole IDs (replaces the full list)
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world write. The description adds one genuinely new behavioral fact: the 256KB image size cap. It says nothing about required permissions, what happens on name collision, or what the call returns, which are material for a mutating endpoint.

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?

A single tight sentence plus an endpoint tag, with the size constraint front-loaded where it matters. Nothing is padding, though the raw HTTP path is arguably redundant for an agent.

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?

For a 5-parameter mutation with no output schema, the definition covers the essentials of what gets uploaded but omits permission requirements and the role-overwrite side effect. Adequate to invoke, thin on what to expect afterward.

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 baseline is 3. The description notes the accepted image sources and adds the 256KB limit not present in the schema. However, it never mentions the roles parameter, which per the schema replaces the full role list — a non-obvious mutation semantic.

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 gives a specific verb and resource: 'Upload a custom emoji'. The POST endpoint path makes the target resource unambiguous. It doesn't explicitly differentiate from create_application_emoji, so it stops short of a 5.

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 on when to use this rather than the application-emoji or sticker counterparts, and no mention of required permissions (e.g. manage-emojis) or preconditions. An agent has to infer usage entirely from the name.

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