Skip to main content
Glama

Slack_connect

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Slack Channel History

slack_channel_history
Read-onlyIdempotent

Get message history from a Slack channel. Bot auto-joins the channel if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax number of messages to return (default 20, max 1000)
cursorNoPagination cursor for next page of results
latestNoOnly messages before this Unix timestamp
oldestNoOnly messages after this Unix timestamp
channelYesChannel ID (e.g., "C01234ABCDE")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoWhether the API call succeeded
errorNoError code if API call failed
messageNoError message or connection message
messagesNoList of messages in the channel
response_metadataNoPagination metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "description": "Error code if API call failed",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message or connection message",
+      "type": "string"
+    },
+    "messages": {
+      "description": "List of messages in the channel",
+      "items": {
+        "properties": {
+          "reply_count": {
+            "description": "Number of replies in thread",
+            "type": "number"
+          },
+          "reply_users_count": {
+            "description": "Number of unique users who replied",
+            "type": "number"
+          },
+          "text": {
+            "description": "Message text content",
+            "type": "string"
+          },
+          "thread_ts": {
+            "description": "Thread timestamp if message is in a thread",
+            "type": "string"
+          },
+          "ts": {
+            "description": "Unix timestamp with milliseconds",
+            "type": "string"
+          },
+          "type": {
+            "description": "Message type (e.g., 'message')",
+            "type": "string"
+          },
+          "user": {
+            "description": "User ID of message sender",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "ok": {
+      "description": "Whether the API call succeeded",
+      "type": "boolean"
+    },
+    "response_metadata": {
+      "description": "Pagination metadata",
+      "properties": {
+        "next_cursor": {
+          "description": "Cursor for next page of results",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "channel": "C01234ABCDE",
+    "limit": 20
+  },
+  {
+    "channel": "C01234ABCDE",
+    "limit": 100,
+    "oldest": "1609459200"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds the auto-join behavior, which is a useful trait not covered by annotations.

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 concise sentences with no wasted words. The description is front-loaded with the core purpose followed by an important behavioral note.

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?

Given the presence of an output schema and detailed parameter schema, the description provides sufficient context (auto-join). It could mention pagination, but that is covered in schema. Overall adequate.

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% with good descriptions for each parameter. The tool description adds no additional parameter meaning beyond what the schema provides, so baseline 3 is appropriate.

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?

The description clearly states the tool gets message history from a Slack channel and adds a key behavioral detail (auto-join). It is distinct from sibling tools like slack_send_message or slack_join_channel.

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 indicates usage for retrieving history but does not explicitly compare with alternatives or specify when not to use it. The auto-join note provides some implicit guidance.

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

All Slack_connect toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources