Skip to main content
Glama

discord_set_role_icon

Idempotent

Assign or remove a custom image or unicode emoji as a role icon. Requires Discord server Boost Level 2+ and Manage Roles permission.

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
guild_idYesDiscord server (guild) ID (snowflake).
role_idYesID (snowflake) of the role to set the icon on.
iconNoImage URL for the role icon, or null to remove it.
unicode_emojiNoUnicode emoji to use as the role icon, or null to remove it.
Behavior4/5

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

The description states the action (set/clear) and that it returns a confirmation. Annotations already indicate idempotentHint=true and destructiveHint=false, so the description adds the operational constraints (Boost level, permissions). No contradictions, and the behavior is adequately disclosed.

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?

The description is three concise sentences: purpose, requirements, and usage/return. It is front-loaded with the key action and avoids unnecessary details.

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

Completeness4/5

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

Given no output schema, the description mentions a confirmation but not error cases. It covers the essential what, prerequisites, and how to clear. For a simple tool, this is fairly complete.

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 100%, so baseline is 3. The description repeats the null-removal semantics already present in the schema. It doesn't clarify behavior when both icon and unicode_emoji are provided, leaving a minor gap.

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 the verb 'Set or clear' and the resource 'a role's icon', specifying both custom image and unicode emoji. It distinguishes itself from sibling tools like discord_edit_role or discord_edit_role_permissions by focusing solely on the icon.

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 explicitly lists prerequisites: Boost Level 2+ and Manage Roles permission. It also explains how to clear the icon by passing null. Although it doesn't mention alternatives or when not to use, the conditions are sufficient for correct invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server