Fetch a guild emoji by ID to verify its existence and inspect role restrictions.
Purpose: Fetch a single guild emoji by ID.
When to use:
Verify an emoji exists; inspect role-restriction list.
Returns: {id, name, animated, available, roles}.
| Name | Required | Description | Default |
|---|---|---|---|
| emoji_id | Yes | Emoji to fetch | |
| guild_id | Yes | Guild owning the emoji |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.28.0Output schema / anyOfPrevious value: -[
- {
- "$schema": "https://json-schema.org/draft/2020-12/schema",
- "additionalProperties": {},
- "properties": {
- "animated": {
- "type": "boolean"
- },
- "available": {
- "type": "boolean"
- },
- "id": {
- "anyOf": [
- {
- "description": "Discord custom emoji ID",
- "pattern": "^\\d{17,20}$",
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "name": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "roles": {
- "items": {
- "description": "Discord role ID",
- "pattern": "^\\d{17,20}$",
- "type": "string"
- },
- "type": "array"
- }
- },
- "required": [
- "id",
- "name",
- "animated",
- "available",
- "roles"
- ],
- "type": "object"
- },
- {
- "properties": {
- "category": {
- "enum": [
- "client",
- "server"
- ],
- "type": "string"
- },
- "code": {
- "type": "string"
- },
- "recovery_hint": {
- "type": "string"
- },
- "retriable": {
- "type": "boolean"
- }
- },
- "required": [
- "code",
- "retriable",
- "category",
- "recovery_hint"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": {},
+ "properties": {
+ "animated": {
+ "type": "boolean"
+ },
+ "available": {
+ "type": "boolean"
+ },
+ "id": {
+ "anyOf": [
+ {
+ "description": "Discord custom emoji ID",
+ "pattern": "^\\d{17,20}$",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "roles": {
+ "items": {
+ "description": "Discord role ID",
+ "pattern": "^\\d{17,20}$",
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "animated",
+ "available",
+ "roles"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "category": {
+ "enum": [
+ "client",
+ "server"
+ ],
+ "type": "string"
+ },
+ "code": {
+ "type": "string"
+ },
+ "recovery_hint": {
+ "type": "string"
+ },
+ "retriable": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "code",
+ "retriable",
+ "category",
+ "recovery_hint"
+ ],
+ "type": "object"
+ }
+]v0.22.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the safety profile is covered. The description adds return fields and use cases but does not disclose behavior like missing-emoji handling or rate-limit implications; this is adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and well-structured with Purpose, When to use, and Returns sections. It is front-loaded and every sentence contributes useful information without filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter read-only fetch with full annotations and an existing output schema, this description is complete. It covers purpose, appropriate use cases, and return shape; nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both guild_id and emoji_id already described meaningfully. The description adds no additional parameter semantics beyond what the schema provides, so the baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Fetch a single guild emoji by ID.' The wording 'single' and 'guild' clearly distinguishes it from siblings like emojis_list_guild and app_emojis_get without needing to inspect them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides a 'When to use' section with two concrete scenarios: verifying an emoji exists and inspecting role-restriction lists. It gives clear context but does not explicitly name alternatives or when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.