Skip to main content
Glama
Sign In
Discord Server Setup MCP

Discord Server Setup MCP

by cj-vana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_role

Permanently delete a role from your Discord server. This action removes the role and its permissions without the ability to undo.

Instructions

Deletes a role from a Discord server. This action cannot be undone.

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": {
      "roleId": "<roleId>"
    },
    "name": "delete_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleIdYesID of the role to delete
guildIdNoGuild ID or name. Defaults to the currently selected guild.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • addedInput schema / properties / guildId / description
      Added value: +"Guild ID or name. Defaults to the currently selected guild."
    • addedInput schema / properties / roleId / description
      Added value: +"ID of the role to delete"
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior3/5

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

The description mentions irreversibility, a key behavioral trait, but lacks details on auth requirements, side effects (e.g., whether members are affected), or error states. With no annotations provided, more transparency would be beneficial.

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?

Two sentences with no wasted words. Every sentence serves a purpose: defining the action and highlighting irreversibility.

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

Completeness4/5

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

Given the simplicity of the tool (2 params, no output schema), the description covers the core purpose and irreversibility. It is adequate but could include more usage context.

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 coverage is 100%, and the description adds no extra meaning beyond the schema's parameter descriptions. Baseline 3 is appropriate.

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 clearly states the action ('deletes') and resource ('role from a Discord server'). It distinguishes from sibling tools like create_role and edit_role by specifying deletion.

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 description implies caution with 'cannot be undone' but does not explicitly state when to use this tool versus alternatives like edit_role, nor mention prerequisites like permissions.

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