Skip to main content
Glama
Sign In
better-discord-mcp

better-discord-mcp

by Sys0xdbg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

discord_edit_welcome_screen

Update a Discord server's welcome screen by specifying the guild ID and custom welcome screen fields.

Instructions

Edit the welcome screen. fields = raw Discord welcome-screen fields.

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": {
      "guildId": "<guildId>",
      "fields": "<fields>"
    },
    "name": "discord_edit_welcome_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYes
guildIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It states 'Edit,' implying mutation, but does not disclose any behavioral traits like required permissions, side effects, or whether the operation is idempotent. This is insufficient for a modification tool.

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?

The description is concise (two short sentences) with no filler. It gets straight to the point, though it sacrifices completeness for brevity.

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

Completeness1/5

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

Given the complexity of modifying a Discord welcome screen (which requires specific object fields), and the lack of annotations, output schema, or parameter descriptions, the description is severely incomplete. It does not inform the agent about return values, error conditions, or how to construct valid inputs.

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

Parameters2/5

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

With 0% schema description coverage, the description says 'fields = raw Discord welcome-screen fields,' which adds some minimal context that the 'fields' parameter expects a raw Discord object. However, it does not explain the required structure or syntax for 'guildId' or 'fields'. The description adds little beyond the schema name.

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 'Edit the welcome screen,' which is a specific verb and resource. It distinguishes from 'discord_get_welcome_screen' (read) among siblings. However, it does not elaborate on what the welcome screen is or what editing entails beyond passing raw fields.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, such as having read the welcome screen first via the sibling tool 'discord_get_welcome_screen'. The description is purely imperative.

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