slack-personal-mcp

Overview Schema Source Related Servers Discussions Admin

slack_read_thread

Read-only

Reads paginated Slack thread messages within timestamp bounds, returning cursors and a complete flag so you can fetch remaining pages up to a configured limit.

Instructions

Read thread pages from cursor within timestamp bounds; all_pages stops at max_pages (default 10). Returns complete=false while more remain. Needs channels:history/groups:history/im:history/mpim:history; users:read.

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": {
      "workspace": "<workspace>",
      "channel_id": "<channel_id>",
      "thread_ts": "<thread_ts>"
    },
    "name": "slack_read_thread"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`latest`	No
`oldest`	No
`all_pages`	No
`inclusive`	No
`max_pages`	No
`thread_ts`	Yes
`workspace`	Yes
`channel_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.3Oct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight here: it discloses pagination semantics ('Returns complete=false while more remain'), the max_pages default and its stop condition, and the exact OAuth scopes required. It does not cover rate limits or ordering of returned messages, but the added context is substantial.

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?

Three short clauses, no filler, and the pagination/default information is front-loaded where an agent will read it. Slightly dense with semicolons, but every clause carries information.

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?

An output schema exists so return values needn't be spelled out, though the description usefully explains the complete flag anyway. For a 10-parameter paginated read with 0% schema coverage, a few parameters (inclusive, limit) remain unexplained, keeping it just short of complete.

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 0% across 10 parameters, so the description must compensate. It meaningfully explains cursor, latest/oldest bounds, all_pages and max_pages, but leaves limit, inclusive, thread_ts, workspace and channel_id (including how to obtain a thread_ts) entirely undocumented.

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 a specific verb and resource ('Read thread pages') and scopes it with cursor and timestamp bounds, which distinguishes it from slack_read_channel (channel-level) and slack_search_messages. It does not name a sibling alternative explicitly, but the thread-vs-channel distinction is clear from the resource named.

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?

The description implies when to use it (when you need a thread's replies, possibly paginated), and gives some operational guidance ('all_pages stops at max_pages'), but never says when to choose this over slack_read_channel or slack_search_messages, nor any prerequisites for obtaining thread_ts.

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