Skip to main content
Glama
Hermoso

Hermoso

Official

Post a Discord announcement

post_to_discord
Destructive

Publish messages, announcements, embeds, polls, and files to a Discord server channel, using the Hermoso bot or a webhook and returning the message ID for edits and replies.

Instructions

Post to the user's Discord server. Free. With the Hermoso bot added it posts as the bot to channel (or the brand's default channel) with attachments up to 25 MB a message, replyTo, threadId (inside a thread), startThread (a thread under the post) and threadName (a forum channel); the messageId it returns ("/") is what edit, delete and get_discord_message take. Without the bot it posts through the brand's announcement webhook (never the alert one): ≤2000 characters, files up to 20 MB attached (up to 10), larger ones as links. Mentions never ping unless mentions:true. EITHER WAY it can carry embeds (up to 10 rich cards, 6000 characters between them), a native poll (question, up to 10 answers, 1 to 768 hours; get_discord_poll reads the votes) and tts (read aloud). A webhook post can also take a display name and avatar for that one post (username, avatarUrl); crosspost:true (bot only) also publishes the post to every server that follows the announcement channel. Anything over a Discord limit is refused, never cut. Reactions are the only per-post number (get_discord_message). Not connected: connect_connector with provider discord and no fields returns the install link.

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": "post_to_discord"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttsNoa text-to-speech message, read aloud to people who have the channel open
hookNothe post's angle — a list_hooks id or your own wording, reused exactly
pollNoa native poll: { question (300), answers: ["..", { text (55), emoji }] (up to 10), durationHours (1-768, default 24), multiselect }. A poll cannot be edited after posting
textNothe announcement, ≤2000 characters
brandNoWHICH PROFILE this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no profile, or two, is REFUSED and nothing is posted.
embedsNoup to 10 embeds: { title (256), description (4096), url, color ("#5865F2" or a number), fields: [{ name (256), value (1024), inline }] (25), author: { name (256), url, iconUrl }, footer: { text (2048), iconUrl }, image, thumbnail (links), timestamp (ISO or "now") }
ideaIdNoshort id of the content-plan idea this post came from
recipeNothe post's FORMAT id, e.g. "slideshow" or "imessage_chat" — post_performance groups by it, so reuse one id per format
silentNopost without a notification
channelNoHERMOSO BOT: channel id or #name (list_discord_channels); unset = the default channel
replyToNoHERMOSO BOT: reply to this message id
subjectNowhat the post is about
imageUrlNo
mentionsNolet @everyone / @here / role mentions ping people (off by default)
threadIdNoHERMOSO BOT: post inside this existing thread
usernameNowebhook posts only: a different display name than the webhook's own
videoUrlNo
avatarUrlNowebhook posts only: an avatar image link for this one post
crosspostNoHERMOSO BOT, announcement channels: also publish it to every server that follows the channel (cannot be undone)
imageUrlsNoup to 10 files in one message
threadNameNorequired when the channel is a FORUM channel: the new thread title
startThreadNoHERMOSO BOT: start a thread under the new post with this title
discordServerNoHERMOSO BOT: which Discord server (id or name) when the bot is in several
allowDuplicateNopost it even though an identical post was just made
idempotencyKeyNoany stable string: a repeat within 24h returns the original post instead of posting again

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.571

TDQS

A4.2/5.0
Behavior5/5

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

Goes far beyond the annotations: discloses bot-vs-webhook behavior, per-message and per-file limits, that oversized content is 'refused, never cut', that mentions are silent by default, and that crosspost 'cannot be undone'. This is exactly the context annotations can't carry.

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-loaded and every clause carries signal, but the long semicolon-joined sentences are dense and hard to parse on first read. Given 25 parameters the compression is defensible rather than wasteful.

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?

For a 25-parameter mutation tool with no output schema, the description covers return value, size limits, mode-dependent capabilities, and the connect fallback well. Minor gaps remain around a handful of metadata params that only the schema documents.

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?

With 92% schema coverage the baseline is 3, and the description earns more by explaining cross-parameter relationships: the returned messageId format that edit/delete/get_discord_message consume, which params are webhook-only vs bot-only, and the mentions:true gating. A few params (hook, recipe, subject, ideaId) get no narrative treatment.

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?

Opens with a clear verb+resource ('Post to the user's Discord server') and the Discord focus implicitly separates it from other platform-post siblings. It does not explicitly name a sibling to contrast with, but the action and target are unambiguous.

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?

Establishes the two operating modes (bot vs webhook) and what changes under each, and routes the unconnected case to 'connect_connector with provider discord'. Lacks explicit when-not guidance relative to other posting tools, but the branching conditions are well covered.

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