Skip to main content
Glama
karbassi

slack-mcp

by karbassi

conversations_list

Retrieve a list of Slack channels with pagination and filtering options. Exclude archived channels or specify types to narrow results.

Instructions

List all channels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor from a previous response's ``response_metadata.next_cursor``.
exclude_archivedNoOmit archived channels from the results.
limitNoMaximum number of channels to return per page (default 100).
team_idNoEncoded team ID to list channels for (for org-wide tokens).
typesNoComma-separated conversation types to include, e.g. ``public_channel,private_channel,mpim,im``.
detailedNoReturn the full, uncompacted Slack response when True.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

No annotations are provided, and the description does not disclose behavioral traits such as pagination, filtering capabilities, or the fact that it lists more than just channels. The description 'List all channels' is inaccurate as it can include DMs and group DMs. This misleads the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is extremely concise (4 words) but lacks structure and clarity. It is too vague and does not earn its place as it omits critical information.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 6 parameters and no output schema, the description is insufficient. It does not explain the output format, pagination behavior, or the effect of parameters like 'types' and 'exclude_archived'. The tool is complex, and the description is incomplete.

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?

The input schema has 100% description coverage for all 6 parameters. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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?

Description says 'List all channels' which is a specific verb+resource, but it's slightly misleading because the tool can list various conversation types (public, private, DMs) as indicated by the 'types' parameter. It does distinguish from siblings like conversations_history and conversations_info, but not precisely.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like conversations_list_connect_invites or other list tools. The context of usage is not provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/karbassi/slack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server