Skip to main content
Glama
larrygmaguire-hash

Slack Note Capture MCP Server

by larrygmaguire-hash
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

slack_read_thread

Retrieve all replies in a Slack message thread to monitor user responses and maintain conversation continuity for asynchronous workflows.

Instructions

Read all replies in a message thread. Use this to check for user responses to a message you posted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idNoThe Slack channel ID. Defaults to configured inbox channel.
thread_tsYesThe timestamp of the parent message.

Implementation Reference

  • src/index.js:431-480 (handler)
    The handler implementation for the 'slack_read_thread' tool, which fetches replies from a thread using the Slack WebClient's conversations.replies method.
    case "slack_read_thread": {
  const channelId = args.channel_id || DEFAULT_CHANNEL;
  const threadTs = args.thread_ts;

  if (!channelId) {
    return {
      content: [
        {
          type: "text",
          text: "Error: No channel ID provided and no default channel configured.",
        },
      ],
    };
  }

  const result = await slack.conversations.replies({
    channel: channelId,
    ts: threadTs,
  });

  const messages = result.messages || [];
  const botId = await getBotUserId();

  // Format messages, marking which are from the bot
  const formattedMessages = messages.map((msg) => ({
    ts: msg.ts,
    text: msg.text,
    user: msg.user,
    is_bot: msg.user === botId,
    date: new Date(parseFloat(msg.ts) * 1000).toISOString(),
  }));

  return {
    content: [
      {
        type: "text",
        text: JSON.stringify(
          {
            channel: channelId,
            thread_ts: threadTs,
            reply_count: formattedMessages.length - 1, // Exclude parent
            messages: formattedMessages,
          },
          null,
          2
        ),
      },
    ],
  };
}
  • src/index.js:141-160 (registration)
    Registration of the 'slack_read_thread' tool including its schema definition.
    {
  name: "slack_read_thread",
  description:
    "Read all replies in a message thread. Use this to check for user responses to a message you posted.",
  inputSchema: {
    type: "object",
    properties: {
      channel_id: {
        type: "string",
        description:
          "The Slack channel ID. Defaults to configured inbox channel.",
      },
      thread_ts: {
        type: "string",
        description: "The timestamp of the parent message.",
      },
    },
    required: ["thread_ts"],
  },
},

Tool Definition Quality

A3.6/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. 'Read' implies safe/non-destructive operation, and 'all replies' suggests completeness, but lacks specifics on error handling (non-existent thread?), pagination, or whether this marks messages as seen.

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 with zero waste. First defines action, second provides use case. No redundant phrases or filler.

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?

Appropriate for a simple read tool with 2 parameters and complete schema coverage. No output schema exists, so description isn't obligated to explain return values, though mentioning the return format (message list) would have been helpful.

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 baseline applies. Description adds semantic context that thread_ts should reference 'a message you posted' (establishing ownership), which helps interpret the parameter purpose beyond the schema's technical definition.

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?

States specific action ('Read all replies') and resource ('message thread'). Implies differentiation from slack_read_messages (channels vs threads) and slack_post_to_thread (read vs write), though doesn't explicitly name siblings.

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?

Provides positive use case ('Use this to check for user responses'), establishing when to use it. Lacks explicit guidance on when NOT to use it (e.g., initial channel reads) and doesn't clarify relationship to slack_wait_for_reply sibling.

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/larrygmaguire-hash/slack-note-capture'

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