Skip to main content
Glama
Oratorian

Discord MCP Server

by Oratorian
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Setup Server Onboarding

discord_setup_onboarding

Set up and enable server onboarding by configuring default channels, multiple-choice or dropdown questions, and role/channel assignments for new members.

Instructions

Setup and enable onboarding for a server from scratch.

This tool configures the complete onboarding experience for new members. The server must have Community features enabled.

Requirements:

  • Server must have Community features enabled (done in Discord Server Settings)

  • At least one default channel must be specified

  • At least one prompt with options must be provided

  • Each option must have at least one role_ids OR channel_ids

Args:

  • guild_id (string): Discord server/guild ID

  • default_channel_ids (string[]): Channels shown to all new members (required, at least one)

  • prompts (array): Onboarding questions (required, at least one)

    • type ('multiple_choice' | 'dropdown'): Prompt type

    • title (string): Question title

    • single_select (boolean): Allow only one selection (default: true)

    • required (boolean): Must answer to continue (default: false)

    • in_onboarding (boolean): Show during onboarding (default: true)

    • options (array): Available choices (at least one)

      • title (string): Option title

      • description (string, optional): Option description

      • emoji_name (string, optional): Unicode emoji (e.g., '🎮')

      • role_ids (string[], optional): Roles to assign when selected

      • channel_ids (string[], optional): Channels to show when selected

  • mode ('onboarding_default' | 'onboarding_advanced', optional): Mode (default: 'onboarding_default')

  • enabled (boolean, optional): Enable after setup (default: true)

Returns: Confirmation with onboarding status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoOnboarding modeonboarding_default
enabledNoWhether to enable onboarding after setup
promptsYesOnboarding prompts/questions (at least one required)
guild_idYesDiscord server/guild ID (snowflake)
default_channel_idsYesChannels shown to new members by default (at least one required)

Tool Definition Quality

A4.2/5.0
Behavior3/5

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

Annotations provide no destructive/intensity hints, but the description states it configures onboarding 'from scratch.' It doesn't cover behavior if onboarding already exists or error cases, which is a gap for a complex tool.

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 well-organized with sections (overview, requirements, args), uses bullet points for clarity, and is concise given the complexity. Every sentence adds value.

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

Completeness4/5

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

The description covers requirements and parameter details thoroughly, and includes a return value note. It lacks error handling or edge cases, but overall is complete for a complex onboarding tool.

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

Parameters4/5

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

Schema describes all parameters (100% coverage), so baseline is 3. The description adds value by specifying requirements and giving context (e.g., 'at least one role_ids OR channel_ids' is clarified beyond schema descriptions).

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

Purpose5/5

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

The description explicitly states 'Setup and enable onboarding for a server from scratch,' making the verb and resource clear. It distinguishes from siblings like discord_edit_onboarding and discord_setup_community.

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 description lists clear requirements (Community features enabled, at least one default channel/prompt/option) and implies it's for initial setup. It could explicitly mention when to use discord_edit_onboarding instead, but the requirements are helpful.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Oratorian/discord-node-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server