TheeDiscordMCP

Overview Schema Source Related Servers Discussions Admin

discord_delete_role

Delete a Discord role permanently by providing the guild ID, role ID, and exact confirmation string. Use dry-run to test before applying.

Instructions

Delete a role with an exact confirmation string.

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": {
      "guildId": "<guildId>",
      "roleId": "<roleId>",
      "confirm": "<confirm>"
    },
    "name": "discord_delete_role"
  }
}

Input Schema

Name	Required	Description	Default
`dryRun`	No
`reason`	No
`roleId`	Yes
`confirm`	Yes
`guildId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits itself. It mentions the confirmation string but omits that deletion is destructive/irreversible, does not explain the dryRun parameter's role, and lacks any mention of permission requirements or failure conditions.

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?

The description is a single concise sentence, easy to parse and front-loaded. However, given the tool's complexity and the importance of the confirmation mechanism, a bit more detail would be warranted without becoming verbose.

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

Completeness2/5

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

This is a destructive tool with 5 parameters, no output schema, and no annotations. The description only covers the confirmation requirement and misses essential context like dryRun behavior, permanent deletion, and permission needs, making it insufficient for safe invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to compensate. It only clarifies the 'confirm' parameter (exact confirmation string) but provides no meaning for guildId, roleId, dryRun, or reason. This is minimal compensation for five parameters.

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 'Delete a role with an exact confirmation string' clearly states the action (delete) and the target resource (role), with a specific condition (exact confirmation string). This distinguishes it from sibling tools like discord_delete_channel or discord_upsert_role.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of preconditions, when deletion would be appropriate, or which sibling tools to use instead.

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