Skip to main content
Glama
Beever-AI

Beever Atlas

Official

list_channels

Retrieve the channels your bot can read on a connection, providing channel IDs, names, and sync status. Use this to obtain a valid channel_id before querying content.

Instructions

List the channels the bot can actually read on one connection — the ground-truth source for what channels exist and their indexing state.

Call this after list_connections/whoami (you need a valid connection_id), once per connection you care about, BEFORE any retrieval tool (ask_channel, search_channel_facts, get_wiki_page, ...) so you can pass a real channel_id. Prefer this over list_connections.selected_channel_count — that count is a sync pick-list, not the channel inventory.

Latency: instant for cached results; may take a few seconds when it queries the live platform bridge. Read-only — does not trigger a sync.

Returns {"channels": [<entry>, ...]} (empty list if none/bridge error). Each entry:

  • channel_id (str): pass to retrieval/sync tools, e.g. "C0A955E29MX".

  • name (str): display name, e.g. "engineering".

  • platform (str): e.g. "slack", "discord", "file".

  • last_sync_ts (str|null): ISO timestamp of last index, null if never.

  • sync_status (str): "synced", "never_synced", or "n/a" (file connections). "never_synced" is normal and does NOT mean the channel is inaccessible — it just is not indexed yet; call trigger_sync(channel_id) to ingest it before querying its content.

  • message_count_estimate (int|null): approx synced messages, null if not yet synced.

Scoping: matches the dashboard "CONNECTED" view. If the user picked specific channels for sync, those are returned; otherwise every channel where the bot is a member (and thus can read) is returned. File connections return every uploaded file.

Error modes: {"error": "connection_access_denied", "connection_id": ...} if you do not own the connection (existence is not leaked); {"error": "invalid_parameter", "parameter": "connection_id"} for a malformed id; {"error": "authentication_missing"} if no principal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connection_idYesId of the connection whose channels to list, obtained from list_connections or whoami. Format: alphanumeric/_/:/- up to 128 chars. Example: "conn_abc123".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses read-only nature (no sync trigger), latency characteristics, error modes, return format with field descriptions, and scoping rules. No contradictions.

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?

Well-structured with clear sections for latency, return format, field descriptions, scoping, and error modes. Every sentence serves a purpose without redundancy.

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?

Despite no output schema provided, the description fully documents the return object structure, field meanings, and error responses. It covers all necessary context for a tool with one required parameter.

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?

Schema coverage is 100% with description for connection_id. The description adds context on where to obtain the parameter (list_connections/whoami) and format requirements, adding value beyond schema.

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 explicitly states it lists channels the bot can read on one connection, serving as ground-truth source. It distinguishes from sibling tools like list_connections and ask_channel by specifying it provides the channel_id needed for retrieval tools.

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

Usage Guidelines5/5

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

Provides precise when-to-call instructions: after list_connections/whoami, before retrieval tools, once per connection. Also recommends preferring this over list_connections.selected_channel_count and explains why.

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/Beever-AI/beever-atlas'

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