Skip to main content
Glama
Slack MCP Server

Slack MCP Server

by ubie-oss

slack_reply_to_thread

Reply to a specific message thread in Slack

Instructions

Reply to a specific message thread in Slack

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>",
      "thread_ts": "<thread_ts>"
    },
    "name": "slack_reply_to_thread"
  }
}

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
thread_tsYesThe timestamp of the parent message in the format '1234567890.123456'. Timestamps in the format without the period can be converted by adding the period such that 6 numbers come after it.
channel_idYesThe ID of the channel containing the thread

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 reply text"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 provided, so the description carries the full burden. It does not state that posting a reply is a visible, externally shared write action, does not mention permission requirements, and does not describe what happens on failure (such as an invalid or nonexistent thread_ts) or what the response contains.

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?

It is a single well-formed sentence with no filler, and the key scoping phrase ('specific message thread') is front-loaded. However, brevity here leans toward under-specification rather than efficiency.

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

Completeness3/5

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

For a 4-parameter, 3-required write tool with no annotations and no output schema, the definition relies almost entirely on the schema. Acceptable because parameter documentation is complete, but the behavioral and usage context an agent needs is largely absent.

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 explains channel_id, thread_ts format, text, and the markdown/slack_mrkdwn format enum. The description adds nothing beyond that, which is the baseline-3 case when the schema does the heavy lifting.

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: 'Reply to a specific message thread in Slack'. This is clearly distinct from reading tools like slack_get_thread_replies, but it never explicitly contrasts itself with slack_post_message, the obvious sibling for new messages.

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?

The phrase 'specific message thread' implies that an existing thread is required, but there is no explicit guidance on when to use reply versus post a new message, no prerequisites, and no exclusions. An agent must infer the choice of tool from the sibling names alone.

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