Skip to main content
Glama

Slack_connect

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Slack List Channels

slack_list_channels
Read-onlyIdempotent

List channels in the Slack workspace. Returns channel names, IDs, and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax number of channels to return (default 100, max 1000)
typesNoComma-separated channel types: public_channel, private_channel, mpim, im (default "public_channel")
cursorNoPagination cursor for next page of results

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "channels": {
+      "description": "List of channel objects",
+      "items": {
+        "properties": {
+          "created": {
+            "description": "Unix timestamp of channel creation",
+            "type": "number"
+          },
+          "creator": {
+            "description": "User ID of channel creator",
+            "type": "string"
+          },
+          "id": {
+            "description": "Channel ID",
+            "type": "string"
+          },
+          "is_channel": {
+            "description": "Whether this is a channel",
+            "type": "boolean"
+          },
+          "is_member": {
+            "description": "Whether the bot is a member",
+            "type": "boolean"
+          },
+          "is_mpim": {
+            "description": "Whether this is a multi-person IM",
+            "type": "boolean"
+          },
+          "is_private": {
+            "description": "Whether the channel is private",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "Channel name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "Error code if API call failed",
+      "type": "string"
+    },
+    "message": {
+      "description": "Error message or connection message",
+      "type": "string"
+    },
+    "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: +[
+  {
+    "limit": 50
+  },
+  {
+    "limit": 100,
+    "types": "public_channel,private_channel"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate read-only, open-world, idempotent, and non-destructive behavior. The description adds that it returns channel names, IDs, and metadata, which is consistent and slightly enhances transparency.

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?

Extremely concise: two sentences, 12 words, no filler. Front-loaded with the core action and output. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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, good annotations, and full parameter schema coverage, the description adequately covers the tool's purpose and output. No missing context.

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 input schema already fully describes all parameters (limit, types, cursor). The description adds no additional meaning beyond what the schema provides.

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?

Description clearly states the tool lists channels in a Slack workspace, with specific verb 'list' and resource 'channels'. It differentiates from sibling tools like slack_channel_history, slack_join_channel, etc., by focusing solely on listing channels.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies usage context (listing channels) but does not explicitly state when not to use or provide alternatives. Sibling tool names help differentiate, but the description itself lacks direct 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