Skip to main content
Glama
Discord MCP Ultimate

Discord MCP Ultimate

discord_publish_announcement

Publish structured Discord announcements with a title, body, fields, color, and optional ping; builds the embed and keeps mentions safe by default, with optional crossposting.

Instructions

Publish a structured announcement to a channel in one call: a title, a body, optional fields, a colour, and an optional ping target. Builds the embed for you so the layout is consistent, and lets you choose the mention policy explicitly instead of relying on the default. SAFE BY DEFAULT for mentions: no mention is parsed unless you pass ping (so '@everyone' inside the body never actually pings). If the channel is an announcement channel and crosspost is true, the message is also published to followers. Requires Send Messages (and Manage Messages to crosspost others' messages).

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": {
      "channel_id": "<channel_id>",
      "title": "<title>",
      "body": "<body>"
    },
    "name": "discord_publish_announcement"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesAnnouncement body (Markdown supported).
pingNoWho to notify. Default 'none': nothing in the body can ping anyone.none
colorNoSide-bar colour.#5865F2
titleYesAnnouncement title.
fieldsNoExtra embed fields (max 25).
footerNoFooter text.
crosspostNoAlso publish to announcement-channel followers, when the channel supports it.
channel_idYesChannel to publish in.
ping_role_idNoRole to ping when ping is 'role'. Required in that case.

Output Schema

NameRequiredDescriptionDefault
pingedYes
channel_idYes
message_idYes
crosspostedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4/5.0
Behavior5/5

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

Goes well past the annotations (readOnly=false, destructive=false, openWorld=true) by disclosing the safety contract — no mention is parsed unless ping is passed, so '@everyone' in the body cannot ping — plus the crosspost-to-followers condition and the required permissions (Send Messages, Manage Messages to crosspost others' messages). These are exactly the mutation-side risks an agent needs before calling.

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?

Front-loads what the tool produces, then the mention-safety rule, then the crosspost conditional and permissions — a sensible priority order. It is somewhat long for a single tool and repeats the schema's ping default, but no sentence is filler.

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

Completeness5/5

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

With an output schema, full annotation coverage and 100% parameter descriptions, the remaining burden is behavioural context — permissions, mention safety, and follower crossposting — and the description covers all three. An agent has everything needed to call it correctly.

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 coverage is 100% and every parameter already carries a description, so the baseline is 3. The description reinforces the ping default ('no mention is parsed unless you pass ping'), which is useful, but it does not explain field layout, limits, or the ping='role' + ping_role_id dependency beyond what the schema states.

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?

States a specific verb and resource — publishes a structured announcement with title, body, fields, colour and ping — and distinguishes itself functionally by noting it 'builds the embed for you so the layout is consistent.' It never names the obvious siblings (discord_send_embed, discord_send_message, discord_crosspost_message), so the agent must infer the split itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: the tool is clearly for one-shot structured announcements, and the crosspost sentence explains a conditional behaviour. But there is no explicit 'use discord_send_embed when you need arbitrary embed JSON' or 'use discord_send_message for plain text' routing, which is the main ambiguity among the many send/crosspost siblings.

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