Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_emoji

Read-only

Retrieve a custom emoji's details from a Discord server by providing the guild ID and emoji ID.

Instructions

Get Guild Emoji. [GET /guilds/{guild_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": {
      "guild_id": "<guild_id>",
      "emoji_id": "<emoji_id>"
    },
    "name": "get_guild_emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
emoji_idYesCustom emoji ID
guild_idYesServer (guild) 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=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing further — no note on permissions needed, rate limits, or whether the emoji must belong to the given guild (an obvious failure mode for a two-ID lookup).

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, so there is no wasted prose. But the brevity borders on under-specification: the single sentence plus endpoint template carries almost no explanatory content, leaving little that 'earns its place' beyond the path.

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 simple two-parameter read with fully documented schema and safety annotations, so the bar is modest. Still, there is no output schema and the description never indicates what is returned (an emoji object and its fields) or how this differs from the similarly named sibling tools, leaving the agent with meaningful blind spots.

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 coverage is 100%, with both guild_id ('Server (guild) ID') and emoji_id ('Custom emoji ID') documented in the schema. The description adds no meaning beyond that, so the baseline of 3 applies; retyping the endpoint template conveys parameter placement but not new semantics.

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 ('Get Guild Emoji') and appends the raw endpoint 'GET /guilds/{guild_id}/emojis/{emoji_id}', which does confirm this fetches a single emoji scoped by guild_id + emoji_id. However, it offers no differentiation from close siblings such as get_emoji_guild or get_application_emoji, so an agent must infer the distinction from names 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 when-to-use, when-not-to-use, or alternative routing guidance. The endpoint path hints that it requires both a guild and emoji ID, but the description never says when this should be chosen over get_emoji_guild or get_application_emoji.

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