Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_top_emojis

Read-only

Retrieves the top emojis for a Discord server by guild ID, helping you identify frequently used custom emojis.

Instructions

List Guild Top Emojis. [GET /guilds/{guild_id}/top-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_top_emojis"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 fully covered. The description adds nothing beyond the HTTP route: no indication of ranking criteria, result count, pagination, or whether the endpoint is rate-limited, which is exactly the kind of context 'top-N' semantics require.

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?

Extremely short and front-loaded, with no filler sentences. The bracketed REST path is the only extra element and is of marginal value, but the brevity itself is not a defect.

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 tool whose distinguishing feature is the word 'top', the definition says nothing about ordering, cutoff, or response shape, and there is no output schema to fill the gap. An agent can issue the call but cannot predict what it gets back or when to prefer it over list_guild_emojis.

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% and the single required parameter guild_id is already documented as 'Server (guild) ID' in the schema. The description adds no extra meaning about the parameter, but with full coverage the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text is essentially the tool name restated ('List Guild Top Emojis') plus the raw REST path '[GET /guilds/{guild_id}/top-emojis]'. It never explains what 'top' means (ranking metric, count returned) or how it differs from the sibling list_guild_emojis, so an agent cannot distinguish the two without trial and error.

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?

No when-to-use guidance, no exclusions, and no mention of the closely named alternative list_guild_emojis. The agent must infer that this returns a ranked subset while the sibling returns the full set.

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