Skip to main content
Glama

Create AutoMod rule

create_automod_rule

Create server-side moderation rules to filter keywords, presets, spam, or member profiles, then block, alert, or timeout offenders.

Instructions

Create a server-side moderation rule that runs on Discord's own infrastructure: Discord-maintained preset word lists (slurs, profanity, sexual content), custom keyword filters (with optional regex), spam detection, mention-flood limits, or member_profile checks on usernames, nicknames, and bios (Community servers only). For slur or hate-speech filtering prefer trigger keyword_preset with the slurs preset: Discord maintains the word list, so none needs to be written. Actions: block the message, alert a channel, and/or time the sender out (timeout is not available on spam, keyword_preset, or member_profile rules). On member_profile rules block quarantines the member until they fix their profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
guildNoGuild (server) name or ID. Omit to use the default guild.
actionsYesWhat happens on a match.
enabledNoDefault true.
presetsNoFor keyword_preset rules: Discord-maintained lists.
triggerYes
keywordsNoFor keyword rules. Wildcards: word* matches prefixes.
allow_listNoWords exempt from keyword and keyword_preset rules.
exempt_rolesNo
alert_channelNoWhere alert actions post.
mention_limitNoFor mention_spam rules: max unique mentions per message.
regex_patternsNoFor keyword rules; Rust-flavored regex.
exempt_channelsNo
timeout_minutesNoHow long timeout actions last.
Behavior4/5

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

Discloses that rules run on Discord's infrastructure, details actions and their effects (e.g., quarantining for member_profile), and notes constraints like Community server requirement. Annotations readOnlyHint=false and destructiveHint=false are consistent with a create 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?

Single paragraph packs substantial detail without redundancy. Slightly dense but efficiently communicates key information; could benefit from bullet points but is still effective.

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 14 parameters and no output schema, the description covers trigger types, actions, constraints, and special cases. Missing minor details about return value, but that is acceptable for a create tool.

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?

Adds meaning beyond schema by explaining relationship between triggers and presets, limitations of timeout, and behavioral differences of member_profile rules. Schema coverage is 71%, and description compensates with useful context.

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 it creates a server-side moderation rule, listing specific trigger types and actions. It distinguishes from siblings like update_automod_rule by focusing on creation and provides specific usage guidance for different triggers.

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?

Provides explicit guidance on when to use keyword_preset for slurs, and notes limitations like timeout unavailability on certain triggers. Does not explicitly state when not to use the tool, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OrygnsCode/Omnicord'

If you have feedback or need assistance with the MCP directory API, please join our Discord server