Skip to main content
Glama
Hermoso

Hermoso

Official

Post a Slack announcement

post_to_slack
Destructive

Publishes text, images, or video to Slack channels, threads, or scheduled posts, and returns a message ID for later editing, deletion, or lookup.

Instructions

Post to the user's Slack. Free. With the Hermoso app installed it posts as the app to channel (or the brand's default channel), uploads images and video, replies in a thread (threadTs) or schedules in Slack (postAt, text only, ≤120 days); the messageId it returns ("/") is what edit_slack_message, delete_slack_message and get_slack_message take. Without the app it posts through the brand's announcement webhook (never the alert one): text ≤40,000 characters (refused, never cut), a title line, png/jpg/gif images by link, video as a link; a webhook post has no id, so it cannot be edited, deleted or measured. Not connected: connect_connector with provider slack 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_slack"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookNothe post's angle — a list_hooks id or your own wording, reused exactly
textNo
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.
titleNoa header line above the text
ideaIdNoshort id of the content-plan idea this post came from
postAtNoHERMOSO APP: schedule in Slack itself for this ISO time (≤120 days, text only; use schedule_post for files)
recipeNothe post's FORMAT id, e.g. "slideshow" or "imessage_chat" — post_performance groups by it, so reuse one id per format
altTextNoalt text for the images
channelNoHERMOSO APP: channel id or #name (list_slack_channels); unset = the default channel
iconUrlNoHERMOSO APP: https picture for that name
subjectNowhat the post is about
imageUrlNo
threadTsNoHERMOSO APP: reply in this thread (the parent message ts)
usernameNoHERMOSO APP: post this text message under this name
videoUrlNo
iconEmojiNoHERMOSO APP: emoji picture, like :rocket:
imageUrlsNo
unfurlLinksNofalse = no link previews
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
replyBroadcastNoHERMOSO APP: also show the thread reply in the channel
slackWorkspaceNoHERMOSO APP: which Slack workspace (id or name) when the app is in several

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.571

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations (destructiveHint=true, openWorldHint=true, idempotentHint=false) by disclosing hard limits and failure behavior: text ≤40,000 characters 'refused, never cut', postAt capped at 120 days and text-only, and that webhook posts have no id and therefore cannot be edited, deleted, or measured. The one residual gap is that it does not restate the irreversible/destructive nature of a live post in a shared channel, leaving that to the annotation.

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 with the app path first and the webhook path second, and nearly every clause carries load-bearing information (limits, return id contract, install fallback). The weakness is formatting: it is delivered as a single semicolon-chained block that is harder to scan than it needs to be at this length.

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?

For a 22-parameter, no-output-schema tool, the description supplies the missing contract: what the call returns ('<channel>/<ts>'), which sibling tools consume it, what happens with and without the app, and the failure modes for oversized text. Nothing an agent needs to call this correctly is missing.

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 82%, so the baseline is 3, but the description adds genuine cross-parameter meaning: it gates postAt, channel, threadTs, username, iconEmoji, iconUrl, replyBroadcast and slackWorkspace to the app path, and explains that the returned messageId is the handle used by edit_slack_message, delete_slack_message and get_slack_message. A few parameters (imageUrl vs imageUrls, unfurlLinks, allowDuplicate, subject, ideaId) get no added explanation beyond their schema text.

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?

States a specific verb and resource ('Post to the user's Slack') and immediately distinguishes two execution modes: direct app posting versus the brand's announcement webhook. An agent can tell exactly what this does and how it differs from siblings like post_to_discord without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes between modes and alternatives: 'With the Hermoso app installed it posts as the app...' versus 'Without the app it posts through the brand's announcement webhook (never the alert one)', plus 'use schedule_post for files' for scheduled file posts. The not-connected path is spelled out too — connect_connector with provider slack and no fields.

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