Skip to main content
Glama

AutoMod rules (admin)

discord_admin_automod
Destructive

Manage Discord AutoMod rules: list, create, enable, disable, or delete keyword, preset, spam, and mention-spam filters; configure block, alert, and timeout actions.

Instructions

List, create, enable, disable or delete AutoMod rules. Triggers: keywords (* wildcards), presets (profanity, sexual_content, slurs), spam, mention_spam. Actions: block, alert a channel, timeout.

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": {
      "action": "<action>"
    },
    "name": "discord_admin_automod"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
allowNoWords that never trigger the rule
blockNoBlock the message
actionYes
reasonNoReason, recorded in Discord's audit log
presetsNo
rule_idNoenable/disable/delete: the rule
triggerNo
keywordsNo
exempt_rolesNo
mention_limitNomention_spam: unique mentions per message
timeout_minutesNoAlso time the author out (keywords / mention_spam only)
alert_channel_idNoPost an alert here
exempt_channel_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the danger profile is covered. The description adds real behavioral context the annotations lack — that keywords support * wildcards, which presets exist, and that rules can block, alert, or time out — but it never says deletion is permanent, whether disabling is reversible, or that these calls require Manage Server rights.

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 short, front-loaded sentences with no filler: the operations first, then triggers, then actions. Every clause carries information an agent would otherwise have to infer from the schema.

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?

For a 14-parameter, destructive, multi-mode tool with no output schema, the description covers the operation set, trigger taxonomy, and action taxonomy, which is the core of what an agent needs. The remaining gaps — permission prerequisites, which parameters are mandatory per action, and what 'list' returns — are meaningful but narrow.

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 50%, so several parameters (keywords, exempt_roles, exempt_channel_ids, name, presets) are undocumented in the schema. The description partially compensates by explaining wildcard syntax for keywords and enumerating preset values, but it says nothing about the exemption lists or how parameters map to the five action values.

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?

The description opens with a specific verb set (list, create, enable, disable, delete) bound to a concrete resource (AutoMod rules), so an agent can tell this apart from the other moderation-adjacent siblings such as discord_admin_lockdown or discord_admin_manage_message. It does not explicitly name a sibling or state what it is not, which keeps it just below a 5.

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 trigger and action enumerations implicitly tell the agent which configuration combinations exist (keywords vs preset vs spam vs mention_spam; block vs alert vs timeout), which is useful orientation. However, there is no explicit when-to-use guidance, no mention of required permissions, and no statement of when an agent should prefer this tool over manual moderation siblings.

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