Skip to main content
Glama
Sign In
discp

discp

by SharimAli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_emojis

List all custom emojis uploaded to a Discord server by server ID so you can discover available emojis for messages.

Instructions

List all custom emojis uploaded to the server

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_emojis"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildIdNoDiscord server ID (defaults to DISCORD_GUILD_ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only operation, whether results are paginated, whether the default guild scope applies when guildId is omitted, or what the returned shape is.

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?

One short, front-loaded sentence with no filler. It is efficient, though it stops short of earning a 5 because it carries almost no information beyond the name.

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?

For a simple one-parameter read tool with full schema coverage and no output schema, the description is minimally adequate. It does not disclose return content (names/IDs/URLs) or the read-only nature, but nothing critical to invoking it is missing.

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%, so the single optional guildId parameter is already documented, including its DISCORD_GUILD_ID default. The description adds no syntax or scoping detail beyond the schema, so the 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?

States a specific verb and resource: list custom emojis uploaded to the server. It is clearly distinguishable from siblings like create_emoji/delete_emoji/get_emoji_details, but it does not explicitly contrast itself with get_emoji_details or list_stickers.

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 mention of prerequisites, and no reference to alternative tools. The agent must infer from the name alone that this is the bulk-enumeration counterpart to get_emoji_details.

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