mcp-saas-toolkit

slack_list_channels

List Slack channels your bot can access, returning their names, IDs, topics, member counts, and purposes. Filter by type, limit results, and exclude archived channels.

Instructions

List Slack channels the bot has access to. Returns channel name, ID, topic, member count, and purpose.

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": "slack_list_channels"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of channels to return (1-200). Default: 100
`types`	No	Comma-separated channel types: public_channel, private_channel, mpim, im. Default: public_channel	public_channel
`exclude_archived`	No	Exclude archived channels. Default: true

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes a read-only operation and states what is returned. However, it does not disclose potential rate limits, authentication requirements, or behavioral constraints like default scope (public channels only), which is partially covered in the schema.

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, concise sentence that conveys the purpose and return fields without superfluous information. It is front-loaded and efficient.

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?

For a list tool with 3 optional parameters and no output schema, the description is fairly complete. It specifies the returned data. It could mention pagination or error handling, but is adequate for its complexity.

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 all parameters have descriptions. The tool description does not add additional meaning beyond what the schema provides. Baseline score of 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 verb 'List' and the resource 'Slack channels', and specifies the returned fields (name, ID, topic, member count, purpose). It distinguishes itself from sibling tools like slack_send_message or slack_add_reaction.

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 does not provide explicit guidance on when to use this tool versus alternatives. It implies the tool is for listing channels, but offers no exclusions or context about when not to use it.

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