Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_application_emoji

Creates a custom emoji for a Discord application by uploading an image from a local path, URL, or data URI, using the app ID and emoji name.

Instructions

Create Application Emoji. [POST /applications/{application_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": {
      "application_id": "<application_id>",
      "name": "<name>",
      "image": "<image>"
    },
    "name": "create_application_emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName
imageYesImage: local file path, http(s) URL or data: URI
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write nature and external-facing behavior are covered structurally. The description adds nothing beyond the endpoint: no note on what happens on name collision, size/format constraints, required permissions, or what the response contains.

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?

It is one short sentence plus an endpoint reference, front-loaded with the verb and resource and free of filler. The bracketed path is slightly redundant with the tool name but still useful routing information.

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 output schema and no explanation of what a successful call returns or how failures manifest. For a creation endpoint with real preconditions, the definition leaves an agent without enough behavioral context to call it confidently.

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 all three parameters (application_id, name, image) are already documented, including the local-path/URL/data-URI forms for image. The description adds no further meaning, so the baseline of 3 applies.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create Application Emoji" restates the tool name, and the bracketed POST path confirms the resource being created. The 'application' scope does implicitly separate it from create_guild_emoji, but the description never states that distinction itself, so the purpose is clear only at a surface level.

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?

There is no guidance on when to use this versus create_guild_emoji or the modify/delete emoji siblings, and no prerequisites (permissions, bot ownership, emoji slot limits) are mentioned. An agent must infer the application-vs-guild split entirely from the tool 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