Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_list_emojis

List custom emojis from a Discord server using its guild ID and an optional result limit to inspect available emoji assets.

Instructions

List custom emoji of a server.

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": {
      "guildId": "<guildId>"
    },
    "name": "discord_list_emojis"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
guildIdYesDiscord id (snowflake)

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?

With no annotations, the description carries the full behavioral burden but discloses almost nothing: no permissions required, no note on whether results are paginated or capped at the default limit of 100, and no hint about what an emoji entry contains. Only the implicit read-only nature of "List" is conveyed.

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?

A single short, front-loaded sentence with zero filler. However, its brevity edges into under-specification rather than disciplined conciseness.

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 simple two-parameter list tool with no annotations and no output schema, an agent still needs to know paging behavior and result shape to call it correctly, and none of that is present. The definition is minimal but leaves real operational gaps.

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 50% — guildId is documented in-schema as a snowflake, while limit has no description. "of a server" loosely reinforces the guildId requirement but adds nothing about the limit parameter's purpose or the maximum of 500, so it neither compensates for nor worsens the gap.

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?

States a specific verb and resource ("List custom emoji of a server"), which is unambiguous and implicitly distinguishes it from the create/delete emoji siblings. It stops short of naming or contrasting with any alternative, but the operation is clear.

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 or when-not-to-use guidance, no mention of alternatives, and no note that guildId requires a target server. The only cue is the word "server," leaving the agent to infer context from the parameter 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