Skip to main content
Glama
Sign In
slack-mcp-server

slack-mcp-server

by dudztroyer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Slack Thread Replies

slack_get_thread_replies

Retrieve all replies from a Slack message thread using channel name or ID and the parent message timestamp.

Instructions

Get all replies in a message thread. Accepts both channel names (#general, general) and channel IDs (C1234567890).

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

Input Schema

NameRequiredDescriptionDefault
channelYesThe channel name (e.g., #general, general) or channel ID (e.g., C1234567890) containing the thread
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.5

TDQS

A3.7/5.0
Behavior3/5

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

Without annotations, the description carries the burden. It correctly implies a read operation but does not disclose rate limits, pagination, or whether all replies are returned. Adequate but minimal.

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 concise sentences, front-loaded with purpose and followed by input flexibility. No wasted words.

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?

A simple tool with 2 required parameters and no output schema. Input format is well explained, but absence of output description (e.g., what each reply object contains) leaves room for improvement.

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 100%, but the description adds value by explaining channel name formats and the thread_ts period conversion, which goes beyond the schema description.

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?

The description clearly states the tool gets all replies in a message thread, using a specific verb and resource. It distinguishes from sibling tools like slack_reply_to_thread which post replies.

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 on when to use this tool versus alternatives like slack_get_channel_history. No context on prerequisites or when not to use it.

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