Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_emojis

Read-only

Fetch all custom emojis for a Discord server using its guild ID, helping you inspect available reaction and expression assets.

Instructions

List a server's custom emojis. [GET /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": "list_guild_emojis"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the REST endpoint path, which gives some context about the underlying API surface. It says nothing about pagination, result limits, or what fields the emoji objects contain.

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 fragments with the purpose front-loaded and no wasted prose. The bracketed endpoint is marginally useful for mapping to API docs but is arguably redundant with the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only list tool with full schema coverage and no output schema, the definition covers what is needed to call it. The main missing piece is disambiguation from the sibling 'top emojis' tool, which matters for correct selection.

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 guild_id parameter, so the schema already explains that it is the server (guild) ID. The description adds no further meaning such as accepted ID formats or whether the bot must be a member. Baseline 3 applies when the schema does the work.

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 and resource ('List a server's custom emojis') and the bracketed endpoint confirms it maps to GET /guilds/{guild_id}/emojis. It does not differentiate itself from the sibling list_guild_top_emojis, so an agent must infer whether this returns all custom emojis or only top ones.

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 the closely related list_guild_top_emojis or list_application_emojis alternatives. The agent is left to infer selection purely 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