Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update server widget

update_server_widget

Configure a Discord server widget by enabling or disabling it or setting its invite channel. Enabling or changing the channel requires a preview and confirm token.

Instructions

Enable or disable the widget, or point its invite channel. An enabled widget shows the server's name, who is online, and its voice channels to anyone on the web, and with an invite channel it lets anyone join. So turning it on, or pointing it at an invite channel while it is on, needs confirming: the first call changes nothing and returns a preview and a confirm_token, and repeating the call with the token makes the change. Turning it off or clearing the channel happens at once.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_server_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoGuild (server) name or ID. Omit to use the default guild.
channelNoInvite channel name or ID, or none to clear.
enabledNo
confirm_tokenNoThe token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / confirm_token
      Added value: +{
+  "description": "The token from this exact action's preview. Where the app can show a confirmation dialog, calling with it asks the user there, and it happens only if they agree.",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is partly covered upstream. The description adds the key behavior annotations cannot express: the two-phase preview/confirm_token protocol, the fact that the first call changes nothing, and that disabling takes effect at once with no confirmation. It does not state permission requirements or what the preview response contains beyond a token.

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?

Three sentences, front-loaded with the actions, then the consequence, then the confirmation rule — nothing extraneous. The middle sentence about public visibility is long but load-bearing because it tells the agent why confirmation exists.

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?

With no output schema, the description compensates by describing what the first call returns (a preview and a confirm_token). For a mutation with four optional parameters and a confirmation handshake, this is close to complete; only permission prerequisites and the exact preview contents remain unstated.

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 coverage is 75%, so guild, channel and confirm_token are already documented; the description still adds real meaning by explaining that confirm_token comes from the immediately preceding preview and that its absence yields a preview rather than a change. It also conveys that clearing the channel is a valid channel value and that enabled controls public exposure, though the default when enabled is omitted is left implicit.

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 opens with specific verbs and the exact resource: "Enable or disable the widget, or point its invite channel." That clearly separates it from the read-only sibling get_server_widget and from the other update_* tools, without the agent needing to open a schema.

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?

It gives unusually precise when-and-how guidance for the confirmation flow: enabling or re-pointing an invite channel on a live widget requires a preview call, while disabling or clearing happens immediately. It does not explicitly name get_server_widget as the inspection alternative, so it falls short of a full when/when-not routing statement.

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