Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_welcome_screen

Read-only

Retrieve a Discord server's welcome screen settings, including description and channel prompts, using the guild ID so you can display or inspect onboarding details.

Instructions

Get Guild Welcome Screen. [GET /guilds/{guild_id}/welcome-screen]

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

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds only the REST endpoint path and discloses nothing about what the welcome screen object contains (description text, enabled flag, welcome channels) or what happens when no welcome screen is configured.

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 short segments with zero padding and the resource identified up front. The bracketed endpoint is arguably redundant with the resource name but is cheap and useful for mapping to the underlying API.

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 single-parameter read tool with full annotation coverage and no output schema, the description is minimally sufficient to invoke correctly. It falls short of describing the returned welcome-screen shape, which an agent would want since no output schema exists.

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 100% and the single guild_id parameter is documented in the schema as 'Server (guild) ID', so the baseline of 3 applies. The description adds no format, sourcing, or constraint detail beyond the schema.

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 names a specific verb and resource ('Get Guild Welcome Screen'), which is enough for an agent to know it retrieves the welcome-screen settings object for a guild. It does not, however, differentiate itself from the similarly named modify_guild_welcome_screen or get_guild_new_member_welcome siblings.

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?

There is no guidance on when to use this tool versus the modify variant or the related new-member-welcome tools. The only additional context is the raw HTTP route, which tells an agent nothing about selection conditions or prerequisites.

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