Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_application_emojis

Read-only

Retrieve all custom emojis for a Discord application by its application ID to inspect or audit the available emojis.

Instructions

List Application Emojis. [GET /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": "list_application_emojis"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 fully covered by structured data. The bracketed '[GET /applications/{application_id}/emojis]' restates the read-only nature implicitly but adds no pagination, filtering, or result-shape detail beyond that.

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?

Two short, front-loaded fragments with no wasted wording. The REST endpoint notation is arguably redundant metadata rather than useful prose, but it costs little.

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?

This is a simple single-parameter read tool with full schema coverage, full annotation coverage, and no output schema, so the bar is low. Still, the description omits what is returned (emoji objects) and any pagination behavior, leaving it minimally viable rather than complete.

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% for the single 'application_id' parameter, so the schema already explains what to supply. The description adds no extra meaning such as where to obtain an application ID or whether it accepts client IDs, so baseline 3 applies.

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 ('List') and resource ('Application Emojis'), which is enough to understand the operation. It does not explicitly distinguish itself from the sibling 'list_guild_emojis', though the 'application' scope in the name and description implies the difference.

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 prerequisites, and no mention of alternatives such as list_guild_emojis or get_application_emoji. The agent must infer usage 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