Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_set_role_icon

Idempotent

Set or clear a role's icon using a custom image URL or unicode emoji. Requires Boost Level 2 and Manage Roles permission; pass null to remove icon.

Instructions

Set or clear a role's icon, either a custom image or a unicode emoji. Requires the server to be Boost Level 2+ (the ROLE_ICONS feature) and the Manage Roles permission. Pass null to either field to remove that icon. Returns a confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconNoImage URL for the role icon, or null to remove it.
role_idYesID (snowflake) of the role to set the icon on.
guild_idYesDiscord server (guild) ID (snowflake).
unicode_emojiNoUnicode emoji to use as the role icon, or null to remove it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed6 schema fields changedv2.0.0
    • addedInput schema / properties / guild_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / icon / anyOf
      Added value: +[
+  {
+    "anyOf": [
+      {
+        "format": "uri",
+        "pattern": "^https?://",
+        "type": "string"
+      },
+      {
+        "const": "null",
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / icon / type
      Removed value: -"string"
    • addedInput schema / properties / role_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / unicode_emoji / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / unicode_emoji / type
      Removed value: -"string"
  3. Changed4 schema fields changedv1.6.0
    • addedInput schema / properties / guild_id / description
      Added value: +"Discord server (guild) ID (snowflake)."
    • changedInput schema / properties / icon / description
      Previous value: -"Image URL for the role icon. Set to null to remove."New value: +"Image URL for the role icon, or null to remove it."
    • addedInput schema / properties / role_id / description
      Added value: +"ID (snowflake) of the role to set the icon on."
    • changedInput schema / properties / unicode_emoji / description
      Previous value: -"Unicode emoji for the role. Set to null to remove."New value: +"Unicode emoji to use as the role icon, or null to remove it."
  4. Addedv1.5.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavioral details: the feature-level requirement (Boost Level 2+), the permission requirement (Manage Roles), the semantics of passing null to clear an icon, and that a confirmation is returned. This goes well beyond what readOnlyHint, idempotentHint, or destructiveHint convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences with no filler: the action comes first, then prerequisites, then null behavior and expected return. Each sentence contributes necessary information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a relatively simple 4-parameter tool with no output schema, the description covers the action, prerequisites, clearing behavior, and return value. Nothing critical is missing for an agent to invoke it correctly.

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 schema already documents all parameters. The description adds context about using either an image or emoji and passing null to clear, but this largely mirrors what the schema already states. It doesn't substantially extend parameter meaning beyond the schema.

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

Purpose5/5

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

The description clearly states a specific action ('Set or clear a role's icon') with a specific resource, and distinguishes the two input forms: custom image or unicode emoji. It is immediately distinguishable from sibling role-related tools like discord_set_role_permission or discord_edit_role.

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

Usage Guidelines4/5

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

The description provides explicit context for when the tool is applicable by stating required server Boost Level 2+ and Manage Roles permission. It doesn't explicitly name alternatives or say when not to use it, but the prerequisites and specific purpose give clear enough guidance.

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