Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_welcome_screen

Updates a Discord server's welcome screen settings, including enabled status, description, and welcome channels, with an optional audit log reason.

Instructions

Modify Guild Welcome Screen. [PATCH /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": "modify_guild_welcome_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
enabledNo
guild_idYesServer (guild) ID
descriptionNo
welcome_channelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the description adds nothing about safety beyond the PATCH marker. For a mutation endpoint it fails to disclose important behavior such as whether omitted/null fields clear existing welcome-screen settings, whether the change is auditable via the reason parameter, or what the response contains. The optional `reason` parameter's audit-log role is only visible in the schema, not the description.

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

Conciseness3/5

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

Very short and front-loaded, so nothing is bloated, but the bracketed HTTP endpoint line is metadata filler rather than agent-useful guidance. Shortness here reflects under-specification rather than disciplined editing.

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?

For a 5-parameter mutation tool with 40% schema coverage, no output schema and no annotations covering semantics, the description is far too thin. The agent knows the route but not the permission requirements, reset/null behavior, or what a successful response returns.

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

Parameters1/5

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

Schema description coverage is only 40% (5 parameters, one required), and the description provides no parameter information whatsoever. It does not explain the semantics of `enabled`, `description`, `welcome_channels`, or `reason`, nor does it clarify that nulls in the anyOf fields may reset values — leaving the agent entirely dependent on terse, partly undocumented schema text.

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

Purpose3/5

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

The description restates the tool name ("Modify Guild Welcome Screen") and appends the HTTP endpoint [PATCH /guilds/{guild_id}/welcome-screen], which at least confirms a mutation on a specific guild sub-resource. It does not distinguish this from the sibling get_guild_welcome_screen or from modify_guild_new_member_welcome, so an agent gets the resource but no differentiation.

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 when-to-use guidance at all: no mention of prerequisites (e.g. needing the guild ID, or MANAGE_GUILD permission), no statement of when to prefer get_guild_welcome_screen first, and no exclusion of the closely related new-member-welcome tool. The only contextual signal is the endpoint path.

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