Discord MCP Ultimate

discord_create_automod_rule

Creates Discord AutoMod rules to filter keywords, spam, mention raids, or suspicious profiles and apply block, alert, timeout, or interaction-block actions.

Instructions

Create an AutoMod rule. Requires Manage Server (Discord gates AutoMod on it) and the server to have the AutoModeration feature, which arrives with Community. Trigger types: 'keyword' (keyword_filter + optional regex_patterns), 'keyword_preset' (Discord's built-in profanity/sexual_content/slurs lists), 'spam', 'mention_spam' (mention_total_limit), 'member_profile' (blocks suspicious profile text). Actions: block_message, send_alert_message (needs channel_id), timeout (needs duration_seconds), block_member_interaction. Returns the created rule.

Input Schema

Name	Required	Description	Default
`name`	Yes	Rule name shown in Server Settings.
`reason`	No	Optional reason recorded in the audit log.
`actions`	Yes	Actions to take on a match.
`enabled`	No	Whether the rule is active on creation.
`presets`	No	Discord's built-in keyword lists (keyword_preset trigger).
`guild_id`	Yes	Discord server (guild) ID (snowflake).
`keywords`	No	Keywords to match (keyword trigger). Max 1000, each up to 60 characters.
`allow_list`	No	Words that are exempt from the keyword filter. Max 100.
`event_type`	No	Which gateway event the rule watches.	message_send
`trigger_type`	Yes	What triggers the rule.
`regex_patterns`	No	Regular expressions to match (keyword trigger). Max 10.
`exempt_role_ids`	No	Roles exempt from the rule.
`exempt_channel_ids`	No	Channels exempt from the rule.
`mention_total_limit`	No	Unique mentions allowed per message before the rule fires (mention_spam trigger).
`mention_raid_protection`	No	Also block messages that mention a role or exceed the limit.

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`actions`	Yes
`enabled`	Yes
`presets`	Yes
`keywords`	Yes
`allow_list`	Yes
`creator_id`	Yes
`event_type`	Yes
`trigger_type`	Yes
`regex_patterns`	Yes
`exempt_role_ids`	Yes
`exempt_channel_ids`	Yes
`mention_total_limit`	Yes
`mention_raid_protection`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0Oct 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already state that this is a non-read-only, non-idempotent, non-destructive write. The description adds meaningful behavioral context: the permission gate, feature availability requirement, trigger-type meanings, action requirements, and that the created rule is returned.

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?

The description is dense but front-loaded and every sentence carries useful information. It covers permissions, trigger types, action requirements, and return behavior without 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 complex 15-parameter tool with full schema descriptions and an output schema, the description supplies enough high-level context to call it correctly. It does not need to restate every schema-level parameter constraint.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3. The description adds useful cross-parameter guidance: keyword triggers pair with keyword_filter/regex_patterns, mention_spam uses mention_total_limit, send_alert_message needs channel_id, and timeout needs duration_seconds.

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 opens with a specific verb and resource: 'Create an AutoMod rule.' This clearly distinguishes it from sibling tools such as discord_edit_automod_rule and discord_delete_automod_rule.

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

Usage Guidelines4/5

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

It gives important usage preconditions: Manage Server permission and the AutoModeration/Community feature. It does not explicitly name edit/list/delete alternatives, but the create context is clear.

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

Deploy Server