Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_guild_automod_rule

Destructive

Deletes a Discord server's AutoMod rule by guild and rule ID, with an optional audit-log reason.

Instructions

Delete Guild AutoMod Rule. [DELETE /guilds/{guild_id}/auto-moderation/rules/{rule_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>",
      "rule_id": "<rule_id>"
    },
    "name": "delete_guild_automod_rule"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/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 is covered structurally. The description only adds the underlying REST endpoint mapping, not irreversibility, permission requirements, audit-log implications of the reason field, or the shape of a successful response. That is thin behavioral context for a destructive operation.

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 fragments with the action front-loaded and no filler. The bracketed endpoint is compact and useful; nothing needs to be cut.

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?

Complete enough for a simple three-parameter destructive endpoint with a fully documented schema and annotations that already flag destruction. Only the missing permission/irreversibility note keeps it below 5.

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%, so guild_id, rule_id and reason are all documented in the schema itself. The bracketed path adds mild information by showing guild_id and rule_id are path parameters, but nothing about reason semantics beyond what the schema states. 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 (Delete) and resource (Guild AutoMod Rule), which clearly separates it from the create/get/modify/list automod siblings and from the many other delete_* tools. It does not explicitly name any alternative, but the resource 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 at all: no prerequisites (e.g. required permissions), no note about when to modify instead of delete, and no mention that the action is permanent. An agent must infer usage entirely from the name.

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