Skip to main content
Glama
Slack MCP Server

Slack MCP Server

by ubie-oss

slack_post_message

Post a new message to a Slack channel

Instructions

Post a new message to a Slack channel

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>",
      "text": "<text>"
    },
    "name": "slack_post_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe message. Written in standard Markdown by default (**bold**, *italic*, headings, lists, tables, code blocks, [label](https://example.com)), which Slack renders.
formatNoHow Slack reads text. markdown (default) renders standard Markdown, up to 12000 characters. slack_mrkdwn reads Slack's own syntax: *bold*, _italic_, ~strike~, <https://example.com|label>.markdown
channel_idYesThe ID of the channel to post to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • addedInput schema / properties / format
      Added value: +{
      +  "default": "markdown",
      +  "description": "How Slack reads text. markdown (default) renders standard Markdown, up to 12000 characters. slack_mrkdwn reads Slack's own syntax: *bold*, _italic_, ~strike~, <https://example.com|label>.",
      +  "enum": [
      +    "markdown",
      +    "slack_mrkdwn"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / text / description
      Previous value: -"The message text to post"New value: +"The message. Written in standard Markdown by default (**bold**, *italic*, headings, lists, tables, code blocks, [label](https://example.com)), which Slack renders."
  2. Addedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only implies a write operation. It says nothing about required permissions/scopes, rate limits, whether the post is visible immediately, or what is returned (e.g., message timestamp) for later threading or reactions.

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?

One short, front-loaded sentence with no wasted wording. It is efficient, though the terseness is part of the tool's under-specification problem rather than a virtue in itself.

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?

For a write tool with zero annotation coverage, the definition omits auth requirements, side effects, return value, and the key routing question of channel post versus thread reply. The rich schema partially compensates, but the description itself is too thin for a mutation tool.

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 description coverage is 100%, including a detailed explanation of the format enum and Markdown rendering, so the schema already does the parameter work. The description adds no additional parameter meaning, which is acceptable at this coverage level.

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 states a specific verb and resource — posting a new message to a Slack channel — which is unambiguous on its own. It does not, however, distinguish this from the sibling slack_reply_to_thread, leaving the top-level-post vs thread-reply boundary unstated.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives. An agent gets no signal that threaded responses should go through slack_reply_to_thread instead of this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.