Skip to main content
Glama
ubie-oss

Slack MCP Server

by ubie-oss

slack_get_thread_replies

Fetch all replies in a Slack thread using the channel ID and parent message timestamp, with optional pagination.

Instructions

Get all replies in a message thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesThe ID of the channel 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.
cursorNoPagination cursor for next page of results
limitNoNumber of replies to retrieve (default 100)

Implementation Reference

  • Main handler for the slack_get_thread_replies tool. Parses request args using GetThreadRepliesRequestSchema, calls slackClient.conversations.replies() with channel_id, thread_ts, limit, and cursor, then parses and returns the response using ConversationsRepliesResponseSchema.
    case 'slack_get_thread_replies': {
      const args = GetThreadRepliesRequestSchema.parse(
        request.params.arguments
      );
      const response = await slackClient.conversations.replies({
        channel: args.channel_id,
        ts: args.thread_ts,
        limit: args.limit,
        cursor: args.cursor,
      });
      if (!response.ok) {
        throw new Error(`Failed to get thread replies: ${response.error}`);
      }
      const parsedResponse =
        ConversationsRepliesResponseSchema.parse(response);
      return {
        content: [{ type: 'text', text: JSON.stringify(parsedResponse) }],
      };
    }
  • Input schema for the slack_get_thread_replies tool. Defines the request structure with channel_id (string), thread_ts (string matching timestamp regex), cursor (optional string), and limit (optional integer, default 100).
    export const GetThreadRepliesRequestSchema = z.object({
      channel_id: z
        .string()
        .describe('The ID of the channel containing the thread'),
      thread_ts: z
        .string()
        .regex(/^\d{10}\.\d{6}$/, {
          message: "Timestamp must be in the format '1234567890.123456'",
        })
        .describe(
          "The 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."
        ),
      cursor: z
        .string()
        .optional()
        .describe('Pagination cursor for next page of results'),
      limit: z
        .number()
        .int()
        .min(1)
        .max(1000)
        .optional()
        .default(100)
        .describe('Number of replies to retrieve (default 100)'),
    });
  • Response schema for the slack_get_thread_replies tool. Extends BaseResponseSchema with an optional array of messages using ConversationsHistoryMessageSchema.
    export const ConversationsRepliesResponseSchema = BaseResponseSchema.extend({
      messages: z.array(ConversationsHistoryMessageSchema).optional(),
    });
  • src/index.ts:142-146 (registration)
    Registers the slack_get_thread_replies tool with its name, description, and input schema (converted to JSON schema via zodToJsonSchema) in the list of available tools.
    {
      name: 'slack_get_thread_replies',
      description: 'Get all replies in a message thread',
      inputSchema: zodToJsonSchema(GetThreadRepliesRequestSchema),
    },
Behavior2/5

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

No annotations exist, so description must disclose behavioral traits. It does not mention pagination, rate limits, or result format. The input schema hints at pagination via cursor and limit, but the description ignores this.

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?

Single front-loaded sentence is concise, but could include more context without losing efficiency. No wasted words.

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 tool with 4 parameters and no output schema or annotations, the description is too brief. It omits pagination behavior, return details, and any usage constraints.

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 baseline is 3. The description adds no parameter context beyond the schema; it only restates the overall purpose.

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?

Description clearly states verb 'Get' and resource 'all replies in a message thread', distinguishing it from sibling tools like slack_reply_to_thread (posts) and slack_get_channel_history (gets channel messages).

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?

No explicit when-to-use or alternatives provided. Usage is implied by the resource name, but no guidance on when not to use or comparison to siblings.

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/ubie-oss/slack-mcp-server'

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