Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_automod_rules

Read-only

List a Discord server’s AutoModeration rules to review content-filtering settings and inspect rule configurations by guild ID.

Instructions

List Guild AutoMod Rules. [GET /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": "list_guild_automod_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the REST path, which hints this is a live Discord API call, but says nothing about required permissions (MANAGE_GUILD), rate limiting, or result ordering.

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?

One short sentence plus bracketed endpoint – front-loaded and free of padding. The endpoint restates structure already implied by the operation and is mildly redundant but not harmful.

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

Completeness3/5

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

For a simple one-parameter read tool with full annotation coverage, this is close to sufficient, but it omits the permission requirement and any hint about what the returned rule objects contain (no output schema exists to compensate). Marginal but real gaps remain.

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% and there is a single required guild_id parameter that the schema documents as "Server (guild) ID". The description adds no meaning beyond that, so the baseline 3 applies.

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 and resource ("List Guild AutoMod Rules") and even cites the underlying endpoint, so an agent knows exactly what it retrieves. It does not distinguish itself from the sibling get_guild_automod_rule, though the plural "Rules" and "List" imply a collection fetch rather than a single fetch.

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 versus get_guild_automod_rule, or whether it is a prerequisite for modify/delete operations that need rule IDs. No prerequisites, no exclusions, no alternatives named.

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