Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_emoji

Rename a Discord server emoji or update which roles are allowed to use it, with an optional audit-log reason.

Instructions

Rename an emoji or change which roles can use it. [PATCH /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": "modify_guild_emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName
rolesNo
reasonNoReason (shown in the audit log)
emoji_idYesCustom emoji ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the write and non-destructive profile and the open-world scope, so the bar is lower. The description adds the endpoint route, but it omits what an agent most needs for a mutation: the permissions required and the fact that the roles list replaces the existing set.

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?

Two short sentences, front-loaded with the capability and followed by the route tag; nothing is wasted. It is efficient, though it uses its brevity at the cost of the caveats noted above.

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 five-parameter mutating endpoint with no output schema, the definition covers the what but not the operating conditions: required permissions, the overwrite semantics of roles, and the audit-log effect of reason. Annotations carry the safety profile, so the gaps are moderate rather than critical.

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 80%, so the schema itself documents all five parameters, including that roles replaces the full list. The description only hints at name and roles, and adds nothing about the reason audit-log parameter.

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-plus-resource pair: rename an emoji or change its role permissions, plus the exact PATCH route. That clearly separates it from create/delete/get emoji siblings, but it says nothing to distinguish it from modify_application_emoji, which is the one sibling it could be confused with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the operation's scope: only name and role visibility can be changed, so an agent can infer it is the tool for edits rather than creation or deletion. There is no explicit when-to-use, no prerequisites such as required permissions, and no statement about when to pick modify_application_emoji instead.

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