discord_delete_role
Delete a role from a Discord server by specifying the guild and role IDs.
Instructions
Deletes a role from a Discord server
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | ||
| roleId | Yes | ||
| guildId | Yes |
Delete a role from a Discord server by specifying the guild and role IDs.
Deletes a role from a Discord server
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | ||
| roleId | Yes | ||
| guildId | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states the core destructive action ('Deletes a role'), which is transparent about the primary effect. However, it does not mention irreversibility, potential cascading effects like permission removals, or required permissions, but since no annotations are present, the description carries the full burden and is reasonably clear.
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 a single concise sentence with no unnecessary words or filler. It directly states the action and target, which is optimal for a simple delete operation.
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?
The description provides the essential 'what' but lacks contextual details such as required permissions, error conditions, or a distinction from removing a role from a member. For a simple deletion, it is adequate but not fully comprehensive.
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?
The input schema has no parameter descriptions, and the tool description does not explain the purpose of guildId, roleId, or reason. The description fails to compensate for the zero schema coverage, leaving parameter semantics entirely unexplained.
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?
The description clearly states the specific action ('Deletes a role') and the resource ('Discord server'), making it unambiguous and distinct from sibling tools like discord_remove_role, which would refer to removing a role from a member.
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?
The description implies when to use this tool (to permanently delete a role definition) but does not explicitly contrast it with alternatives such as discord_remove_role (removing a role from a member) or discord_edit_role. No explicit 'when not to use' guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/barryyip0625/mcp-discord'
If you have feedback or need assistance with the MCP directory API, please join our Discord server