Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_guild_role

Destructive

Delete a Discord guild role by providing the server ID and role ID, with an optional audit log reason to record why the role was removed.

Instructions

Delete a role. [DELETE /guilds/{guild_id}/roles/{role_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>",
      "role_id": "<role_id>"
    },
    "name": "delete_guild_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
role_idYesRole ID
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile and external side effects are known without the description. The description adds the REST endpoint mapping, which helps an agent reason about the underlying API, but it says nothing about irreversibility, what happens to members holding the role, or permission requirements.

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 clauses, front-loaded with the action and followed by the endpoint reference. Nothing is padded, though the endpoint echo is close to redundant with the schema and adds little beyond traceability.

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 three-parameter destructive delete, the annotations plus the full schema coverage carry most of the burden. What is missing is the consequence model: whether role assignments are removed, whether the action is recoverable, and what permissions are needed — relevant because this is the sole role-deletion tool.

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%, with guild_id, role_id, and the optional audit-log reason all documented in the schema. The endpoint path in the description implicitly confirms guild_id and role_id are path parameters, but adds no new meaning; baseline 3 applies.

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 and resource ('Delete a role') and pins it to the exact endpoint DELETE /guilds/{guild_id}/roles/{role_id}, so it is unmistakable against siblings like create_guild_role or modify_guild_role. It stops short of naming an alternative explicitly, but the verb+resource pair is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of related tools such as remove_member_role (which removes an assignment rather than the role itself). An agent must infer the distinction from the tool name alone.

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