discord-mcp

Edit server settings (admin)

discord_admin_edit_server

Destructive

Update Discord server settings, including name, description, icon, banner, verification level, notifications, content filter, channels, and AFK timeout.

Instructions

Change the server's name, description, icon or banner (https image URL, or "none"), verification level, default notifications, content filter, system / rules / AFK channel and AFK timeout. Channels: ID, or "none".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discord_admin_edit_server"
  }
}

Input Schema

Name	Required	Description
`name`	No
`locale`	No	e.g. "en-US", "en-GB", "hi"
`reason`	No	Reason, recorded in Discord's audit log
`icon_url`	No
`banner_url`	No	Needs boost level 2
`description`	No
`verification`	No
`afk_channel_id`	No
`content_filter`	No
`rules_channel_id`	No	Community servers only
`system_channel_id`	No
`afk_timeout_minutes`	No
`default_notifications`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the mutation profile is known. The description adds real value by explaining that icon/banner accept an https URL or "none" (i.e. clearing existing assets), but it omits the crucial question for a 13-optional-param tool: whether omitted fields are left unchanged or reset, and what permissions are required.

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 dense sentences that front-load the field enumeration with no filler, and the trailing channel clause is properly scoped. Very slightly telegraphic ("Channels: ID, or 'none'") but every phrase carries information.

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 13-parameter, all-optional destructive mutation with no output schema, the description covers the field surface well but leaves the partial-update semantics, permission requirements, and any return/confirmation behavior unspecified. The absence of an output schema means the agent cannot learn the result shape anywhere else, so a sentence about what is returned would have closed the gap.

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 only 31%, so the description must compensate, and it partly does by mapping prose field names to parameters and explaining the "ID or none" convention for channels and the image-URL convention for icon/banner. However, two parameters — locale and reason (audit-log justification) — receive no mention at all, and afk_timeout_minutes is described only as "AFK timeout" without units.

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?

Names a specific verb ("Change") and target ("the server's") and enumerates every mutable field — name, description, icon/banner, verification, notifications, content filter, channels, AFK timeout. An agent can tell this is the server-level settings editor rather than discord_admin_edit_channel or discord_admin_edit_role, though the description never states that distinction explicitly.

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?

Usage is implied by the enumerated settings — you call it when you need to change server-level configuration. There is no explicit when-not guidance, no mention of required permissions (Manage Server), and no pointer to discord_admin_get_server for reading current values first, despite that sibling existing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server