discord-mcp

guild_modify_welcome_screen

Idempotent

Update a Discord community's welcome screen: toggle enabled, set a description, and fully replace the up-to-5 highlighted channels (pass null to clear the description).

Instructions

Purpose: Update the Community welcome screen.

When to use:

Toggle enabled, change top description, swap the up-to-5 highlighted channels.

welcome_channels is the FULL replacement list (no PATCH-merge). Pass null for description to clear.

Returns: {description, welcome_channels}.

Input Schema

TableJSON Schema

Name	Required	Description
`enabled`	No
`guild_id`	Yes	Guild to modify
`description`	No
`audit_reason`	No	Reason recorded in audit log (X-Audit-Log-Reason header)
`welcome_channels`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.28.0Sep 15, 2026

removedInput schema / properties / welcome_channels / items / properties / emoji_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedInput schema / properties / welcome_channels / items / properties / emoji_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedInput schema / properties / welcome_channels / items / properties / emoji_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedInput schema / properties / welcome_channels / items / properties / emoji_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "description": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "welcome_channels": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "channel_id": {
-              "description": "Discord channel ID (snowflake)",
-              "pattern": "^\\d{17,20}$",
-              "type": "string"
-            },
-            "description": {
-              "type": "string"
-            },
-            "emoji_id": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "emoji_name": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "required": [
-            "channel_id",
-            "description",
-            "emoji_id",
-            "emoji_name"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "description",
-      "welcome_channels"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "category": {
-        "enum": [
-          "client",
-          "server"
-        ],
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "recovery_hint": {
-        "type": "string"
-      },
-      "retriable": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "code",
-      "retriable",
-      "category",
-      "recovery_hint"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "$schema": "https://json-schema.org/draft/2020-12/schema",
+    "additionalProperties": {},
+    "properties": {
+      "description": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "welcome_channels": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "channel_id": {
+              "description": "Discord channel ID (snowflake)",
+              "pattern": "^\\d{17,20}$",
+              "type": "string"
+            },
+            "description": {
+              "type": "string"
+            },
+            "emoji_id": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "emoji_name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "channel_id",
+            "description",
+            "emoji_id",
+            "emoji_name"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "description",
+      "welcome_channels"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "category": {
+        "enum": [
+          "client",
+          "server"
+        ],
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "recovery_hint": {
+        "type": "string"
+      },
+      "retriable": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "code",
+      "retriable",
+      "category",
+      "recovery_hint"
+    ],
+    "type": "object"
+  }
+]

First observedv0.22.0Aug 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description discloses a critical non-obvious behavior: `welcome_channels` is a FULL replacement list with no PATCH-merge, which warns the agent not to partially update this field. It also explains the null semantics for `description`, adding value beyond the annotations and preventing accidental clearance or overwrite.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, uses bold labels for scanning, and front-loads the purpose before the usage conditions. The critical replacement caveat is isolated in its own line so the agent is likely to notice it; every sentence carries necessary information.

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

Completeness5/5

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

The description provides everything needed to invoke the tool correctly: purpose, when-to-use, the crucial replace-not-merge behavior, the null-to-clear semantics, and the return shape. The schema covers structural constraints, and the description complements it rather than repeating it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 40% schema description coverage, the description compensates for the key parameters: it covers `enabled` via 'toggle enabled', `description` via the null-to-clear note, and `welcome_channels` via full-replacement semantics. The schema already documents `guild_id`, `audit_reason`, and channel IDs, so no major parameter is left unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Update the Community welcome screen.' The 'When to use' list enumerates the exact operations (toggle enabled, change description, swap highlighted channels), clearly distinguishing this from the broader guild_modify tool and other guild-level tools.

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

Usage Guidelines4/5

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

The description provides explicit usage scenarios with the 'When to use' bullet list, telling the agent exactly the circumstances under which this tool applies. It does not explicitly mention alternatives to avoid, but the stated contexts are clear enough for selection among sibling tools.

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

Deploy Server