discord-mcp

guild_get_welcome_screen

Read-onlyIdempotent

Fetch a Discord server's Community welcome screen to review onboarding configuration before making changes.

Instructions

Purpose: Fetch the configured Community welcome screen.

When to use:

Inspect onboarding before tweaking it.

Returns: {description, welcome_channels:[{channel_id, description, emoji_id, emoji_name}], untrusted_text}. Descriptions remain raw server-owner data; untrusted_text provides a separately fenced copy.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`guild_id`	Yes	Guild to query

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.28.0Sep 15, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "additionalProperties": {},
-    "properties": {
-      "description": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "untrusted_text": {
-        "type": "string"
-      },
-      "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",
-      "untrusted_text"
-    ],
-    "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"
+        ]
+      },
+      "untrusted_text": {
+        "type": "string"
+      },
+      "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",
+      "untrusted_text"
+    ],
+    "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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds value beyond the annotations by warning that descriptions are raw server-owner data and that untrusted_text is a separately fenced copy. This gives useful security-relevant behavior without contradicting the annotations.

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 and well-structured with clear Purpose, When to use, and Returns sections. Every sentence contributes meaningful information, and the most important info is front-loaded.

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?

For a simple single-parameter read-only tool with rich annotations and an output schema, the description covers the purpose, use context, return shape, and an important trust boundary. Nothing essential is missing for an agent to invoke it correctly.

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?

The input schema already documents the only parameter, guild_id, as 'Guild to query', with 100% schema description coverage. The description adds no additional parameter-level details, so the 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 a specific verb and resource: 'Fetch the configured Community welcome screen.' It is unambiguous about what the tool does. It does not explicitly distinguish itself from the sibling onboarding_get or guild_modify_welcome_screen, but the resource-specific wording makes confusion unlikely.

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 'When to use' section provides a clear context: 'Inspect onboarding before tweaking it.' This tells an agent when the tool is relevant. However, it does not mention when not to use it or name alternatives such as onboarding_get, so it stops short of the fullest guidance.

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

Deploy Server