Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

execute_automod_alert_action

Triggers a Discord AutoModeration alert action for a specific guild message and channel, with an optional audit-log reason.

Instructions

Execute AutoMod Alert Action. [POST /guilds/{guild_id}/auto-moderation/alert-action]

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>",
      "channel_id": "<channel_id>",
      "message_id": "<message_id>",
      "alert_action_type": "<alert_action_type>"
    },
    "name": "execute_automod_alert_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
channel_idYesChannel ID
message_idYesMessage ID
alert_action_typeYesalert action type

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, openWorldHint=true, and the POST route is consistent with a write. Beyond that, the description discloses nothing about what the mutation does, required permissions, or which alert_action_type values are valid; with annotations carrying the safety profile this is far below a useful level of added context.

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, but the brevity comes from under-specification rather than discipline; the endpoint fragment occupies the one informative slot that could have explained behavior.

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?

This is a 5-parameter mutating moderation tool with no output schema and no explanation of what an alert action does or returns. Given the complexity and the openWorldHint flag, the definition leaves an agent unable to predict the effect of a 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 the baseline is 3. However alert_action_type is typed only as "number" with a vague label and no enum, and the description does not compensate by listing the accepted action types or explaining the interaction between guild_id, channel_id, and message_id.

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?

"Execute AutoMod Alert Action" is a near-verbatim restatement of the tool name; the bracketed POST route only identifies the HTTP endpoint, not what the action does to the alert or message. An agent cannot tell from this how it differs from modify_automod_incident_actions or resolve_automod_incident.

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, what preconditions must hold (message must have triggered an AutoMod alert), or which sibling to pick for incident resolution versus alert actions. Use is implied only by 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