Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_automod_incident_actions

Update a Discord server's AutoMod incident action settings, including when DMs or invites are disabled, and record an audit log reason.

Instructions

Modify AutoMod Incident Actions. [PUT /guilds/{guild_id}/incident-actions]

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": "modify_automod_incident_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
dms_disabled_untilNodms disabled until (ISO8601 time)
invites_disabled_untilNoinvites disabled until (ISO8601 time)

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 state readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The bracketed PUT verb weakly implies replacement/idempotent semantics, but the description never says what happens to dms_disabled_until or invites_disabled_until when omitted, nor what permissions are needed. A mutation tool with this much unstated consequence deserves more than an HTTP verb.

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?

Two short fragments with zero fluff, and the endpoint is placed after the name. It is efficiently sized, but the brevity comes from under-specification rather than from tight writing of substantive content.

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 4-parameter mutation tool with no output schema, the definition supplies no return behavior, no permission requirements, no effect of omitted fields, and no relationship to the incident lifecycle siblings. The only real content is the route annotation, which leaves the agent underspecified before a write call.

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 all four parameters (guild_id, reason, dms_disabled_until, invites_disabled_until) are self-documenting. The description adds nothing about parameter meaning or about which action each timestamp toggle controls; baseline 3 applies.

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?

"Modify AutoMod Incident Actions" restates the tool name almost verbatim without explaining what an incident action is or what modifying it means. The only added signal is the bracketed endpoint [PUT /guilds/{guild_id}/incident-actions], which hints at scope but does not describe the operation in agent-readable terms.

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 and no mention of any alternative, despite siblings like modify_guild_automod_rule, resolve_automod_incident, and report_automod_incident that could easily be confused with this one. The agent must guess whether this tool sets, extends, or clears an incident's action state.

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