Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update AutoMod rule

update_automod_rule

Change an AutoMod rule's name, toggle it on or off, or replace its keyword list. Risky changes like turning a rule off return a preview and confirm_token, so nothing applies until you confirm.

Instructions

Rename a rule, enable or disable it, or replace its keyword list. Turning a rule off, or a new list that leaves out keywords the rule has now, stops it catching what it caught, so that needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Renaming, turning a rule on, and adding keywords happen at once.

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": {
      "rule": "<rule>"
    },
    "name": "update_automod_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
ruleYesRule name or ID.
guildNoGuild (server) name or ID. Omit to use the default guild.
enabledNo
keywordsNoReplaces the keyword list on keyword rules.
confirm_tokenNoThe token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token
      Added value: +{
+  "description": "The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.3/5.0
Behavior5/5

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

The description carries essential behavior the annotations do not: a preview-then-confirm flow where the first call changes nothing and returns a confirm_token, and a repeat call performs the change. It also discloses that certain edits take effect immediately. This is exactly the kind of conditional mutation safety information annotations cannot express.

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 sentences, front-loaded with the actions, then the confirmation caveat, then the immediate-effect cases. The longer middle sentence is dense but every clause carries necessary behavioral information. No filler.

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 six-parameter mutation with no output schema, the description covers the critical two-step flow and which edits are instant. Remaining gaps, such as what happens when the preview is abandoned or on invalid rule identifiers, are minor. Adequate to invoke correctly.

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 67%, so some description-side explanation is needed. The description clarifies that 'keywords' replaces the list and that omitted existing keywords cause lost coverage, and it explains the confirm_token flow meaningfully. It leaves 'name' (new name) and 'enabled' largely to the schema, but overall adds useful meaning beyond the structured fields.

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 set and resource: 'Rename a rule, enable or disable it, or replace its keyword list.' That distinguishes it cleanly from create_automod_rule/delete_automod_rule without needing to name them. It stops short of explicitly routing away from delete_automod_rule when the intent is just to disable, so not a full 5.

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?

Explains precisely when the two-step confirmation path is triggered: turning a rule off or sending a keyword list that drops existing keywords. It also states which operations bypass confirmation ('Renaming, turning a rule on, and adding keywords happen at once'). It does not explicitly contrast with siblings like delete_automod_rule, but the when-to-use 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

Other Tools