Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_application_emoji

Update an application's custom emoji name using its application ID and emoji ID, letting you rename bot or app emojis via the Discord API.

Instructions

Modify Application Emoji. [PATCH /applications/{application_id}/emojis/{emoji_id}]

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>",
      "emoji_id": "<emoji_id>"
    },
    "name": "modify_application_emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName
emoji_idYesCustom emoji ID
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description's only additional signal is the bracketed PATCH verb, which hints at partial-update semantics, but it does not state which fields can be changed, whether omitted fields are preserved, or what permissions are required.

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

Conciseness3/5

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

It is short and front-loaded with no filler, but the brevity reflects under-specification rather than efficiency. The bracketed HTTP path is low-value metadata for an agent that already has the tool name.

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?

For a mutation tool with three parameters, the description omits what the operation returns, what fields are editable, and whether the change is partial or full. Annotations and the schema cover safety and parameter identity, but the description leaves the agent guessing about the operation's effect.

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 are already documented in the schema. The description adds no parameter-level meaning, which is acceptable at full coverage but earns only the baseline score.

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?

The description restates the tool name ('Modify Application Emoji') and adds the HTTP route, which does establish that it targets an application-scoped emoji rather than a guild emoji. However, it never says what 'modify' actually changes (the schema shows only 'name' is updatable), so the purpose is named but not explained.

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 when-to-use guidance, no mention of prerequisites, and no differentiation from siblings such as modify_guild_emoji, create_application_emoji, or delete_application_emoji. The agent must infer the choice from the tool name alone.

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