Skip to main content
Glama
inboxd
by 47star

list_slack_conversations

Find Slack public/private channels, DMs, and group DMs by channel or participant name/email; returns conversation IDs for scoped message search, recent messages, and thread lookup.

Instructions

Find Slack channels, personal DMs and group DMs by channel name or participant name/email.

Returns conversation_id for scoped search, recent messages and thread lookup, plus known participants and per-conversation backfill state. kind selects public_channel, private_channel, dm or group_dm. user_id is an exact Slack user ID. account is a Slack workspace ID. Matching requires collected metadata; unknown membership may omit name/user matches. Continue with next_cursor and unchanged filters. Does not query or write to Slack remotely.

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_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryNo
cursorNo
accountNo
user_idNo
include_archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the tool operates on locally collected metadata and 'does not query or write to Slack remotely,' plus the pagination contract and the incomplete-match caveat. It omits ordering guarantees, behavior on empty query, and any permission/auth expectations.

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

Conciseness4/5

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

The purpose is front-loaded in the first clause and the density is justified given seven undocumented parameters. A few phrases are compressed to the point of ambiguity, e.g. 'Returns conversation_id for scoped search, recent messages and thread lookup' reads as a run-together list rather than a clear return description.

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?

There is no output schema, so the description usefully names the returned fields (conversation_id, known participants, per-conversation backfill state). Combined with the pagination and metadata-limitation notes, an agent has enough to call it correctly, with the main residual gap being limit and include_archived semantics.

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 0% across 7 parameters, so the description must compensate. It explains kind (four allowed values), user_id (exact Slack user ID), account (workspace ID), query (channel name or participant name/email), and cursor/next_cursor reuse, but leaves limit and include_archived entirely undocumented by either source.

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 first sentence gives a specific verb and resource: find Slack channels, personal DMs and group DMs, filtered by channel name or participant name/email. It also positions the tool as the discovery step that produces conversation_id for downstream search/thread lookups, which implicitly separates it from siblings like search_messages and get_slack_thread. It never names an actual sibling, so it falls short of full explicit differentiation.

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?

The description tells the agent when results may be incomplete (matching requires collected metadata; unknown membership may omit name/user matches) and how to page (continue with next_cursor and unchanged filters), which is actionable usage context. It does not state explicit exclusions such as which tool to use instead when the workspace has not been synced.

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