Skip to main content
Glama
lars-hagen

Slack User MCP Server

by lars-hagen

slack_reply_to_thread

Post replies to specific message threads in Slack channels using channel ID, thread timestamp, and reply text.

Instructions

Reply to a specific message thread in Slack

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.
textYesThe reply text

Implementation Reference

  • Switch case handler for 'slack_reply_to_thread' tool: validates arguments and invokes slackClient.postReply to execute the reply.
    case "slack_reply_to_thread": {
      const args = request.params
        .arguments as unknown as ReplyToThreadArgs;
      if (!args.channel_id || !args.thread_ts || !args.text) {
        throw new Error(
          "Missing required arguments: channel_id, thread_ts, and text",
        );
      }
      const response = await slackClient.postReply(
        args.channel_id,
        args.thread_ts,
        args.text,
      );
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Core implementation in SlackClient that posts a reply to a thread using Slack's chat.postMessage API with thread_ts parameter.
    async postReply(
      channel_id: string,
      thread_ts: string,
      text: string,
    ): Promise<any> {
      const response = await fetch("https://slack.com/api/chat.postMessage", {
        method: "POST",
        headers: this.headers,
        body: JSON.stringify({
          channel: channel_id,
          thread_ts: thread_ts,
          text: text,
          as_user: this.isUserToken
        }),
      });
    
      return response.json();
    }
  • Tool definition with name, description, and input schema specifying required parameters: channel_id, thread_ts, text.
    const replyToThreadTool: Tool = {
      name: "slack_reply_to_thread",
      description: "Reply to a specific message thread in Slack",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: {
            type: "string",
            description: "The ID of the channel containing the thread",
          },
          thread_ts: {
            type: "string",
            description: "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.",
          },
          text: {
            type: "string",
            description: "The reply text",
          },
        },
        required: ["channel_id", "thread_ts", "text"],
      },
    };
  • index.ts:535-544 (registration)
    Registration of the tool in the list returned by ListToolsRequest handler.
    tools: [
      listChannelsTool,
      postMessageTool,
      replyToThreadTool,
      addReactionTool,
      getChannelHistoryTool,
      getThreadRepliesTool,
      getUsersTool,
      getUserProfileTool,
    ],
  • TypeScript interface defining the expected arguments for the slack_reply_to_thread tool.
    interface ReplyToThreadArgs {
      channel_id: string;
      thread_ts: string;
      text: string;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits like permissions needed, rate limits, error handling, or whether it's idempotent. It lacks details on what happens if the thread doesn't exist or if the reply fails.

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?

The description is a single, front-loaded sentence with zero waste, efficiently conveying the core purpose without unnecessary details. It's appropriately sized for the tool's complexity.

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?

Given no annotations and no output schema, the description is incomplete for a mutation tool. It doesn't explain return values, error cases, or behavioral nuances, leaving significant gaps in understanding how the tool behaves in practice.

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 the schema already documents all parameters thoroughly. The description adds no additional meaning beyond implying the parameters are used for replying to threads, which is redundant. Baseline 3 is appropriate as 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 clearly states the action ('Reply to') and target ('a specific message thread in Slack'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'slack_post_message' (which might post to channels rather than threads), leaving room for ambiguity.

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 is provided on when to use this tool versus alternatives, such as 'slack_post_message' for non-threaded messages or 'slack_add_reaction' for reactions. The description assumes context but offers no explicit usage rules or exclusions.

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/lars-hagen/slack-user-mcp'

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