Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_automod_rule

Update an existing AutoMod rule in a Discord server to change its name, trigger, actions, enabled state, or exempt roles and channels, with an optional audit log reason.

Instructions

Modify Guild AutoMod Rule. [PATCH /guilds/{guild_id}/auto-moderation/rules/{rule_id}]

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>",
      "rule_id": "<rule_id>"
    },
    "name": "modify_guild_automod_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName
reasonNoReason (shown in the audit log)
actionsNoactions
enabledNoEnabled
rule_idYesAutoMod rule ID
guild_idYesServer (guild) ID
event_typeNoevent type
exempt_rolesNoexempt roles
exempt_channelsNoexempt channels
trigger_metadataNotrigger metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds only the HTTP verb/path and says nothing about PATCH semantics (whether omitted fields are preserved or cleared), audit-log implications, or failure behavior for a missing rule.

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?

Two short, front-loaded fragments with zero filler. It is appropriately sized only because the endpoint line carries most of the informational weight; nothing is wasted, though little is offered.

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 nested objects and no output schema, the description is far too thin. An agent still needs to know that this is a partial update, that the rule must exist, and how omitted vs. supplied fields behave, none of which is stated.

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%, so every parameter is documented in the schema and the baseline is 3. The description adds no extra meaning about what each field does or how nested objects like trigger_metadata and actions are structured, so it neither helps nor harms this dimension.

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 states a specific verb (Modify) and resource (Guild AutoMod Rule) and even names the underlying endpoint, so an agent can tell the operation apart from create/delete/get siblings. It stops short of explicitly differentiating those siblings, but the purpose is unambiguous.

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 guidance on when to use this tool versus the sibling create/delete/get AutoMod tools, nor any prerequisites (e.g., rule must already exist, permissions needed). The endpoint alone implies a mutation but does not route the agent.

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