MCP OpsBridge

slack_get_thread

Retrieve messages from a Slack thread by providing the channel ID and thread timestamp. Adjust the limit to control how many messages are returned, up to a maximum of 100.

Instructions

Retrieve messages in a thread

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>",
      "ts": "<ts>"
    },
    "name": "slack_get_thread"
  }
}

Input Schema

Name	Required	Description
`ts`	Yes	Thread timestamp
`limit`	No	Max messages to return
`channel`	Yes	Channel ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 10, 2026

TDQS

B3.1/5.0

Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states the basic action and does not mention pagination behavior, ordering, error conditions for invalid thread timestamps, rate limits, or authentication requirements. This is minimal coverage for a tool that reads potentially large thread data.

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, clear, front-loaded sentence with no unnecessary words. It efficiently states the tool's purpose without redundancy.

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?

The tool is relatively simple, and the schema fully documents parameters. However, the description lacks usage guidance and return-value details, and with no annotations or output schema, the overall context is thinner than ideal. It is minimally viable but leaves room for improvement regarding thread specifics and alternative tools.

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?

The input schema has 100% description coverage for all three parameters, so the schema already explains the meaning of 'channel', 'ts', and 'limit'. The description adds no additional parameter-level detail beyond what is in the schema, which is acceptable given the schema's thoroughness.

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 verb 'Retrieve' and the resource 'messages in a thread', which distinguishes it from channel-level operations like slack_get_channel_history. However, it does not explicitly mention that a thread is identified by channel and ts, though this is implied by the schema.

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 like slack_get_channel_history or slack_send_thread_reply. The intended use case (retrieving thread messages) is implied by the name and description, but there are no explicit when-to-use or when-not-to-use instructions.

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