discord-mcp

Delete role (admin)

discord_admin_delete_role

Destructive

Permanently delete a Discord role by specifying its name or ID and matching the exact role name to confirm; use after user confirmation because the action cannot be undone.

Instructions

Permanently delete a role. Cannot be undone. confirm_name must equal the role's exact name. Confirm with the user first.

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": {
      "role": "<role>",
      "confirm_name": "<confirm_name>"
    },
    "name": "discord_admin_delete_role"
  }
}

Input Schema

Name	Required	Description
`role`	Yes	Role name or ID
`reason`	No	Reason, recorded in Discord's audit log
`confirm_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the irreversibility flag is somewhat redundant; however the description adds genuinely new behavioral context – the required confirmation step and the exact-match constraint on confirm_name. It omits permission requirements and the side effect of stripping the role from members.

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?

Four short, front-loaded sentences with no filler. The irreversible warning and confirmation instruction come first, which is exactly right for a destructive operation.

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 destructive admin mutation with no output schema, the definition covers safety and the confirmation parameter well, but leaves out permission prerequisites and the downstream effect on members who hold the role. Adequate, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description compensates for the weakest gap by explaining confirm_name's exact-match semantics, which the schema leaves undocumented. The reason parameter's audit-log meaning is already in the schema, so no credit there, but the overall semantic coverage is solid for three parameters.

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: 'Permanently delete a role.' The purpose is unambiguous and easily distinguished from siblings like discord_admin_create_role or discord_admin_edit_role, though it doesn't explicitly name those alternatives.

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?

Offers a safety workflow ('Confirm with the user first') which is real usage guidance for a destructive tool, but says nothing about when to delete versus edit/rename, or about prerequisite conditions like needing Manage Roles permission.

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

Deploy Server