Keeploop

List Slack channels

list_slack_channels

Read-only

List the Slack conversations Keeploop can read (channels, private channels, direct messages and group direct messages), how many messages of each it keeps, and who it reads Slack as. A bot reads only channels it was invited to; the visibility field says exactly what is and is not visible. Read only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_slack_channels"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`count`	Yes
`reader`	No
`backfill`	No
`channels`	Yes
`kept_days`	Yes
`workspace`	No
`visibility`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026
RemovedOct 12, 2026
First observedOct 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already state readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond annotations: bot visibility is limited to channels the bot was invited to, and the `visibility` field clarifies what is visible. It does not describe pagination or rate limits, but the added authorization/visibility detail 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it states what is listed, what metadata is returned, and the visibility caveat in two efficient sentences. Every sentence adds useful information without waste.

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?

With zero parameters, an output schema present, and annotations covering the safety profile, the description supplies the remaining context an agent needs: the scope of readable Slack conversations and the bot-invite visibility limitation. Nothing essential for correct invocation appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so parameter semantics are not a concern. Per the baseline for zero-parameter tools, a 4 is appropriate; the description does not need to explain inputs beyond confirming the listing behavior.

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 gives a specific verb and resource: it lists Slack conversations Keeploop can read, and it enumerates the relevant conversation types plus the extra metadata returned. It does not explicitly contrast itself with `search_slack` or `get_slack_thread`, so it falls short of full sibling differentiation.

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 the tool is useful by explaining that it reports readable Slack conversations and visibility, but it does not explicitly say when to choose this over `search_slack` or how to proceed after listing channels. The 'Read only' note is useful but is not a usage guideline.

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

All Keeploop tools Inspect

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.