Discord Server Setup MCP

Overview Schema Source Related Servers Discussions Admin

update_server_settings

Update your Discord server's name, description, verification level, content filter, and default notifications in a single operation.

Instructions

Updates multiple server settings at once. Can modify name, description, verification level, content filter, and default notifications.

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

Input Schema

Name	Required	Description
`name`	No	New server name (2-100 characters)
`guildId`	No	Guild ID or name. Defaults to the currently selected guild.
`description`	No	New server description (community servers, max 300 characters)
`verificationLevel`	No	Verification level for new members
`explicitContentFilter`	No	Explicit content filter setting
`defaultMessageNotifications`	No	Default notification setting for new members

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv2.0.1Jul 4, 2026
- addedInput schema / properties / defaultMessageNotifications / description
```
Added value: +"Default notification setting for new members"
```
- addedInput schema / properties / description / description
```
Added value: +"New server description (community servers, max 300 characters)"
```
- changedInput schema / properties / description / maxLength
```
Previous value: -120New value: +300
```
- addedInput schema / properties / explicitContentFilter / description
```
Added value: +"Explicit content filter setting"
```
- addedInput schema / properties / guildId / description
```
Added value: +"Guild ID or name. Defaults to the currently selected guild."
```
- addedInput schema / properties / name / description
```
Added value: +"New server name (2-100 characters)"
```
- addedInput schema / properties / verificationLevel / description
```
Added value: +"Verification level for new members"
```
First observedv2.0.0Feb 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so description carries the full burden. The description only states 'updates' without detailing mutation implications, required permissions, error cases, or return values. Minimal behavioral disclosure.

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?

The description is concise: one sentence with a clear verb and resource, followed by a list of fields. It is front-loaded with the key information and has no fluff.

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?

Given 6 parameters, no annotations, and no output schema, the description is insufficient. It does not explain the return value, partial update behavior, or error handling. The tool's complexity demands more context.

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 coverage is 100% (each parameter has a description in the input schema). The description adds a listing of fields but no extra semantic context beyond what the schema already provides. Baseline 3 is appropriate.

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?

The description clearly states it updates server settings and lists the modifiable fields. It implies batch update capability, which distinguishes it from sibling tools that set individual settings, but could be more explicit.

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?

No guidance on when to use this tool versus the individual set_* siblings. The description does not mention prerequisites, constraints, or alternatives.

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