Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_automod_rule

Creates a Discord AutoMod rule in a server to automatically filter content and apply actions. Define trigger, event type, and actions to block spam or harmful messages.

Instructions

Create Guild AutoMod Rule. [POST /guilds/{guild_id}/auto-moderation/rules]

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>",
      "name": "<name>",
      "event_type": "<event_type>",
      "trigger_type": "<trigger_type>",
      "actions": "<actions>"
    },
    "name": "create_guild_automod_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName
reasonNoReason (shown in the audit log)
actionsYesactions
enabledNoEnabled
guild_idYesServer (guild) ID
event_typeYesevent type
exempt_rolesNoexempt roles
trigger_typeYestrigger type
exempt_channelsNoexempt channels
trigger_metadataNotrigger metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write/external scope is known. The description contributes nothing further: no permission requirements, no statement that the rule becomes active immediately and enforces moderation, and no success/failure behavior — the only added text is the REST verb and path.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with no filler, so nothing is wasted, but the terseness reflects under-specification rather than disciplined editing. The bracketed route is the only information not already in the name.

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

Completeness2/5

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

For a 10-parameter mutation with 5 required fields, opaque numeric enums, and no output schema, this definition is far too thin — an agent cannot tell what a valid trigger_metadata looks like, what event_type values are accepted, or whether creation requires validation or specific permissions.

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 100% (each of the 10 params has a description), so the baseline is 3 even though the description adds no parameter meaning. Notably it does not explain the numeric event_type/trigger_type values or the shape of trigger_metadata, which the schema labels only as 'event type' and 'trigger metadata'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text is essentially the tool name restated ('Create Guild AutoMod Rule') plus the raw HTTP route. It does convey a create operation on an automod rule, but adds no distinguishing detail versus siblings like modify_guild_automod_rule or validate_guild_automod_rule beyond what the name already encodes.

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: no statement of prerequisites (e.g., needing Manage Server permission), no mention of when to validate first with validate_guild_automod_rule, and no note that modify/delete siblings exist for edit/removal flows. The agent must infer all routing 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