Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_new_member_welcome

Update a Discord server's new-member welcome settings, including enablement, welcome message, resource channels, and actions, to control how new members are greeted and onboarded.

Instructions

Modify Guild New Member Welcome. [PUT /guilds/{guild_id}/new-member-welcome]

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_new_member_welcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
enabledNoEnabled
guild_idYesServer (guild) ID
welcome_messageNowelcome message
resource_channelsNoresource channels
new_member_actionsNonew member actions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 safety profile is covered structurally. The description contributes nothing further: it does not say whether omitted fields are cleared or preserved, that a reason appears in the audit log, or what permissions are needed for a guild-level configuration write.

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?

Two short fragments, so there is no wasted prose, but the second fragment is a raw HTTP path that duplicates structured information rather than front-loading useful intent. Brevity here reflects under-specification more than disciplined conciseness.

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?

This is a mutation tool with nested-object parameters and no output schema, so the description should carry the behavioral load. It instead supplies only a name and endpoint, leaving partial-update semantics, permission requirements, and effect on the guild's onboarding flow entirely unexplained.

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%, so all six parameters (guild_id, reason, enabled, welcome_message, resource_channels, new_member_actions) are already documented in the schema. The description adds no format or semantics beyond that, which is the expected baseline when the schema does the heavy lifting.

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 New Member Welcome") and appends the raw endpoint PUT /guilds/{guild_id}/new-member-welcome. It does convey a mutation of a specific guild-configuration resource, but adds no scope detail beyond the name, so an agent learns little it could not infer from the identifier alone.

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: nothing distinguishes this from get_guild_new_member_welcome (the read counterpart) or from the adjacent modify_guild_welcome_screen, and no prerequisites or side conditions are stated. The verb 'Modify' weakly implies a write operation, which is the only implicit usage cue.

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