Skip to main content
Glama
karbassi

slack-mcp

by karbassi

chat_post_message

Send a message to any Slack channel, direct message, or thread. Supports text, Block Kit blocks, attachments, and threaded replies.

Instructions

Send a message to a channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYesID of the channel to post to (e.g. ``C0123``), or a DM ID (``D0123``) or user ID for a DM.
textNoMessage text or fallback text when ``blocks`` are provided. Supports Slack mrkdwn.
attachmentsNoLegacy attachment array. Prefer ``blocks`` for new messages.
blocksNoBlock Kit block array defining the message layout.
as_userNoPost as the authenticated user rather than as the bot (legacy; ignored for workspace apps).
icon_emojiNoEmoji to use as the bot icon, overrides the app default (e.g. ``:robot_face:``); needs ``username``.
icon_urlNoURL of an image to use as the bot's icon. Requires ``username``.
link_namesNoFind and link channel names and usernames in ``text`` (e.g. ``#general`` → hyperlink).
metadataNoStructured metadata object attached to the message (``event_type`` + ``event_payload``).
mrkdwnNoRender Slack mrkdwn formatting in ``text`` (default True).
parseNoHow to handle message text: ``full`` (linkify everything) or ``none`` (pass text as-is).
reply_broadcastNoAlso post the threaded reply to the channel when ``thread_ts`` is set.
thread_tsNoTimestamp of the parent message to reply to, forming a thread (e.g. ``1700000000.000100``).
unfurl_linksNoAutomatically unfurl URL links in the message.
unfurl_mediaNoAutomatically unfurl media URLs (images, video) in the message.
usernameNoOverride the bot's display name for this message.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

The description only states the action without disclosing side effects (e.g., message creation, notifications), required scopes (e.g., chat:write), or error handling. With no annotations, the description should provide more behavioral context, but it does not.

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?

The description is a single concise sentence with no extraneous words. However, for a tool with many parameters, a slightly longer description could add value without losing conciseness.

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

Completeness2/5

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

Given the complexity (16 parameters, output schema exists), the minimal description is insufficient. It lacks typical usage examples, auth requirements, and mention of output schema, making it incomplete for effective agent invocation.

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%, so the schema already documents all parameters. The description adds no additional meaning beyond the schema's parameter descriptions. Baseline of 3 is appropriate.

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?

The description 'Send a message to a channel' clearly states the verb (send) and resource (message to a channel), distinguishing it from siblings like chat_delete or chat_update. However, it could specify the platform (Slack) and does not explicitly differentiate from chat_post_ephemeral.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like chat_post_ephemeral, chat_schedule_message, or chat_stream. Missing prerequisites or context for selection.

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/karbassi/slack-mcp'

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