Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild

Update Discord server settings such as name, icon, banner, description, verification level, system/rules/AFK channels, and ownership to reconfigure a guild.

Instructions

Edit server settings: name, icon, banner, description, verification level, system/rules/AFK channels, ownership… [PATCH /guilds/{guild_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>"
    },
    "name": "modify_guild"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoCode
iconNo
nameNoName
bannerNo
reasonNoReason (shown in the audit log)
splashNo
featuresNoGuild feature flags (e.g. ["COMMUNITY"])
guild_idYesServer (guild) ID
owner_idNoTransfer ownership to this user ID
afk_timeoutNoAFK timeout in seconds (60, 300, 900, 1800, 3600)
descriptionNo
home_headerNo
afk_channel_idNo
discovery_splashNo
preferred_localeNoPreferred locale, e.g. en-US
rules_channel_idNo
system_channel_idNo
verification_levelNoVerification level 0-4 (none, low, medium, high, very high)
system_channel_flagsNosystem channel flags
explicit_content_filterNoMedia filter: 0 off, 1 members without roles, 2 everyone
safety_alerts_channel_idNo
public_updates_channel_idNo
premium_progress_bar_enabledNopremium progress bar enabled
default_message_notificationsNo0 all messages, 1 only @mentions
owner_configured_content_levelNoowner configured content level

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is covered. The description adds that this is a partial PATCH and reveals the audit-log `reason` semantics only via the schema, but it omits important behavior: whether omitted fields are preserved, what permissions the caller needs, and that ownership transfer is a high-impact, hard-to-reverse operation despite destructiveHint=false.

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?

A single front-loaded sentence with the resource first and the field list followed by the endpoint annotation — efficient and easy to scan. The trailing ellipsis is slightly loose, hinting at fields not listed, but no sentence is wasted.

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 25-parameter mutation with no output schema, the description covers the headline fields and the HTTP verb, which is the minimum needed to call it. It still leaves out partial-update semantics, required permissions, image-resolution behavior, and side effects of ownership transfer, so it is adequate rather than complete.

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?

With 25 parameters and only 56% schema description coverage, the description partially compensates by naming name, icon, banner, description, verification level, system/rules/AFK channels and ownership. But it does not clarify the image-input convention (local path / URL / data URI), the numeric encoding choices, or how null is used to clear a field, so roughly half the parameters remain ambiguous.

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?

Uses a specific verb plus resource ("Edit server settings") and enumerates the concrete guild-level fields affected, ending with the underlying PATCH /guilds/{guild_id} endpoint. This lets an agent distinguish guild-level settings from the many sub-resource siblings (modify_guild_role, modify_guild_emoji, modify_guild_widget), though it never explicitly names those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use statement; guidance is only implied by the field list, which signals 'top-level guild settings' rather than sub-resources like roles or emojis. An agent must infer the boundary from the enumerated fields and the endpoint path.

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