Skip to main content
Glama
r28ai

Sales Prep MCP

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

slack_chat_post_message

Send a message to a Slack channel, private group, or DM. Provide text for a plain message, or set thread_ts to reply inside an existing thread.

Instructions

Send a message to a Slack channel, private group, or DM. Provide text for a plain message; set thread_ts to reply inside an existing thread.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoThe main body text of the message. Required unless blocks or attachments are provided. Used as the fallback string for notifications when blocks are provided, so it is worth setting even then.
parseNoChange how messages are treated. Accepts 'none' or 'full'.
blocksNoA JSON-based array of structured Block Kit blocks.
mrkdwnNoDisable Slack markup parsing by setting to false. Defaults to true.
channelYesAn encoded ID or channel name that represents a channel, private group, or IM channel to send the message to. Prefer the encoded ID (e.g. 'C123ABC456').
iconUrlNoURL to an image to use as the icon for this message. Requires the chat:write.customize scope.
metadataNoApplication-specific metadata to attach to the message.
threadTsNoProvide another message's 'ts' value to make this message a reply in that thread. Avoid using a reply's ts value; use the parent's.
usernameNoSet the bot's user name. Requires the chat:write.customize scope.
iconEmojiNoEmoji to use as the icon for this message, e.g. ':chart_with_upwards_trend:'. Requires the chat:write.customize scope.
linkNamesNoFind and link user groups.
attachmentsNoA JSON-based array of structured attachments.
unfurlLinksNoPass true to enable unfurling of primarily text-based content.
unfurlMediaNoPass false to disable unfurling of media content.
markdownTextNoAccepts message text formatted in markdown. Limit this field to 12,000 characters. Cannot be used together with blocks or text.
replyBroadcastNoUsed in conjunction with thread_ts and indicates whether the reply should be made visible to everyone in the channel. Defaults to false.
unfurlAppLinksNoPass true to enable unfurling of links to installed apps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write/external nature is covered. The description adds the threading behavior, but does not disclose required scopes, rate limits, message-size limits, or what a successful send returns — and most scope info already lives in the schema parameter descriptions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and then the two most important parameter behaviors. No filler or redundancy.

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 17-parameter tool with no output schema, the description is thin but the schema carries full parameter documentation, so an agent can call it correctly. Missing behavioral context (rate limits, required scopes, response shape) keeps it from a 5.

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%, so all 17 parameters are documented in the schema itself. The description's notes on `text` and `thread_ts` largely restate what the schema already provides, so the baseline of 3 is appropriate.

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 ('Send') and resource ('a message to a Slack channel, private group, or DM'), making the action and destination unambiguous. An agent can distinguish this from siblings like slack_conversations_create 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 Guidelines3/5

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

The second sentence gives implied usage for `text` and `thread_ts`, but there is no explicit when-to-use vs. when-not, no mention of prerequisites (e.g. chat:write scope), and no reference to alternative messaging tools such as gmail_messages_send. Usage is implied rather than stated.

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