Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_application_emoji

Read-only

Retrieves a Discord application's custom emoji by application ID and emoji ID, so you can inspect emoji details before using or managing it.

Instructions

Get Application Emoji. [GET /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": "get_application_emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
emoji_idYesCustom emoji ID
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the REST endpoint path, with no mention of permissions needed, whether the emoji is scoped to an application versus guild, or what happens for unknown IDs.

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?

The description is a single short line that is front-loaded with the verb and resource. The bracketed HTTP route is arguably redundant noise for an agent but does no harm and stays brief.

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 simple two-parameter read tool with full schema coverage and annotations, the description is minimally adequate. It does not clarify the returned emoji object or its distinction from the guild emoji variants, which is the main remaining gap given no output schema.

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%, with both emoji_id and application_id documented in the schema itself. The description adds no additional meaning about their format or constraints, 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?

The description states a specific verb and resource ('Get Application Emoji') plus the REST route, so the basic action is identifiable. However, it offers no differentiation from closely named siblings such as list_application_emojis, get_guild_emoji, or get_emoji_source, leaving the agent to infer the distinction from the name alone.

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 tool versus the list endpoint or any of the other emoji retrieval tools. No prerequisites, no exclusions, no conditions are stated.

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