Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_delete_role

Destructive

Permanently remove a Discord role from the server, stripping it from all members. Requires Manage Roles permission and the role must be below the bot's highest role.

Instructions

Permanently delete a role from the server; it is automatically removed from every member who held it. IRREVERSIBLE. Requires the Manage Roles permission, and the role must be below the bot's highest role.

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": "discord_delete_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional reason recorded in the server audit log.
role_idYesID (snowflake) of the role to delete.
guild_idYesDiscord server (guild) ID (snowflake).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / guild_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / role_id / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed3 schema fields changedv1.6.0
    • addedInput schema / properties / guild_id / description
      Added value: +"Discord server (guild) ID (snowflake)."
    • addedInput schema / properties / reason / description
      Added value: +"Optional reason recorded in the server audit log."
    • addedInput schema / properties / role_id / description
      Added value: +"ID (snowflake) of the role to delete."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the bar is lowered; the description adds substantial context beyond that: the cascading removal from all members, explicit irreversibility, the Manage Roles permission requirement, and the hierarchy constraint relative to the bot's highest role. Nothing contradicts the annotations.

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?

Three sentences, each earning its place: the core action, the cascade consequence, and the prerequisites/irreversibility warning. Front-loaded with the verb and resource; zero filler.

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

Completeness5/5

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

For a 3-parameter tool with full schema coverage, no nested objects, and no output schema (delete endpoints typically return nothing), the description covers every decision-critical fact: what is destroyed, side effects on members, irreversibility, permission, and hierarchy. An agent can determine whether and how to invoke it correctly.

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%, so the schema already documents guild_id, role_id, and reason; the baseline 3 applies. The description adds only peripheral param context (the hierarchy constraint on role_id), not format or syntax detail beyond the schema.

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?

States a specific verb and resource: 'Permanently delete a role from the server.' The cascade note ('automatically removed from every member who held it') disambiguates from sibling discord_remove_role, which unassigns a role from a member without deleting the role itself.

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?

The prerequisites ('Requires the Manage Roles permission, and the role must be below the bot's highest role') give clear conditions for when the call will succeed, and 'IRREVERSIBLE' warns against casual use. However, it never names alternatives (e.g., discord_edit_role to modify, discord_remove_role to unassign instead), leaving when-not-to-use to inference.

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