Skip to main content
Glama

channels_list

Read-onlyIdempotent

📋 The messaging channels connected to this workspace and whether they are working.

One row per channel account: channel, display_name, status, error, and reconnect_url when the account needs repair. A channel in status 'error' is NOT receiving messages — say so plainly and give the person reconnect_url; it opens the repair directly, so do not tell them to look for it in settings and do not build a link of your own.

An account connected through channels.connect_session carries the external_ref it was started with.

Pass only_broken=true to check for outages without listing the healthy channels.

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

Input Schema

NameRequiredDescriptionDefault
chatsNoWith account_id: that account's chats, synced or NOT (search.threads sees only synced ones). A text finds the chats whose title contains it, e.g. 'showcase' finds 'Server › #showcase' of a big Discord server left out for its size; '*' lists them all. At most 50 per answer, synced first, then by kind and title; `chats_page` says total, has_more and next_offset. Each comes with thread_id, synced, why it is out of sync, member_count, and for a Discord server channel its topic, can_view and can_send (false = this account may not read / post there, null = unknown). Turn one on with threads.update(thread_id=..., synced=true). OMIT otherwise.
account_idNoOne account in detail, with its large_group_threshold (groups this large are left out of sync; change it with channels.sync_settings). For a custom channel this adds whether it is listening or polling, why inbound is down, how many contacts it has, the progress of a history import, a health check and the agents that would answer on it. For Discord: whether the gateway stream is up (connected_at, last event), how many servers, server channels and DMs the account sees, how many chats are synced and the sync scope. OMIT to list the workspace's channels.
only_brokenNotrue = only the accounts that need attention (status 'error'). OMIT to list every channel of the workspace.
chats_offsetNoWith chats: skip this many chats, to read the next page (pass chats_page.next_offset). OMIT for the first page.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / chats / description
      Previous value: -"With account_id: find that account's chats whose title contains this text, synced or NOT (search.threads sees only synced ones), e.g. 'showcase' finds 'Server › #showcase' of a big Discord server left out for its size. Each comes with thread_id, synced, why it is out of sync, member_count, and for a Discord server channel its topic and can_send (false = this account may not post there, null = unknown). Turn one on with threads.update(thread_id=..., synced=true). OMIT otherwise."New value: +"With account_id: that account's chats, synced or NOT (search.threads sees only synced ones). A text finds the chats whose title contains it, e.g. 'showcase' finds 'Server › #showcase' of a big Discord server left out for its size; '*' lists them all. At most 50 per answer, synced first, then by kind and title; `chats_page` says total, has_more and next_offset. Each comes with thread_id, synced, why it is out of sync, member_count, and for a Discord server channel its topic, can_view and can_send (false = this account may not read / post there, null = unknown). Turn one on with threads.update(thread_id=..., synced=true). OMIT otherwise."
    • addedInput schema / properties / chats_offset
      Added value: +{
      +  "description": "With chats: skip this many chats, to read the next page (pass chats_page.next_offset). OMIT for the first page.",
      +  "type": "integer"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / account_id / description
      Previous value: -"One account in detail, with its large_group_threshold (groups this large are left out of sync; change it with channels.sync_settings). For a custom channel this adds whether it is listening or polling, why inbound is down, how many contacts it has, the progress of a history import, a health check and the agents that would answer on it. OMIT to list the workspace's channels."New value: +"One account in detail, with its large_group_threshold (groups this large are left out of sync; change it with channels.sync_settings). For a custom channel this adds whether it is listening or polling, why inbound is down, how many contacts it has, the progress of a history import, a health check and the agents that would answer on it. For Discord: whether the gateway stream is up (connected_at, last event), how many servers, server channels and DMs the account sees, how many chats are synced and the sync scope. OMIT to list the workspace's channels."
    • addedInput schema / properties / chats
      Added value: +{
      +  "description": "With account_id: find that account's chats whose title contains this text, synced or NOT (search.threads sees only synced ones), e.g. 'showcase' finds 'Server › #showcase' of a big Discord server left out for its size. Each comes with thread_id, synced, why it is out of sync, member_count, and for a Discord server channel its topic and can_send (false = this account may not post there, null = unknown). Turn one on with threads.update(thread_id=..., synced=true). OMIT otherwise.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / account_id / description
      Previous value: -"One account in detail. For a custom channel this adds whether it is listening or polling, why inbound is down, how many contacts it has, the progress of a history import, a health check and the agents that would answer on it. OMIT to list the workspace's channels."New value: +"One account in detail, with its large_group_threshold (groups this large are left out of sync; change it with channels.sync_settings). For a custom channel this adds whether it is listening or polling, why inbound is down, how many contacts it has, the progress of a history import, a health check and the agents that would answer on it. OMIT to list the workspace's channels."
  4. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "One account in detail. For a custom channel this adds whether it is listening or polling, why inbound is down, how many contacts it has, the progress of a history import, a health check and the agents that would answer on it. OMIT to list the workspace's channels.",
      +  "type": "integer"
      +}
  5. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  6. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real operational context beyond them: that status 'error' means messages are NOT being received, that `reconnect_url` opens the repair directly and must not be reconstructed, and that `external_ref` appears for connect_session accounts. It does not discuss rate limits or result-size behavior beyond the 50-chat cap, which is a minor gap.

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?

Front-loaded with the resource and the row shape, then the error-handling instruction, then the parameter hints. Every sentence carries information, though the reconnect_url instruction is slightly verbose and the parameter notes could be tighter.

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?

With no output schema, the description carries the burden of describing return values, and it does so by enumerating the row fields and the error/reconnect semantics. Combined with a fully documented 5-parameter schema, an agent has enough to call this correctly; only pagination and volume behavior are lightly covered.

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%, so the baseline is 3, but the description adds meaning on top: it explains the purpose of `only_broken` in workflow terms and clarifies that `account_id` switches from a list to a single-account detail view. The `chats` and `in_workspace` parameters are left entirely to the schema, which is acceptable given the rich schema text.

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 opening line names the specific resource (messaging channels connected to this workspace) and the key attribute (whether they are working), and the row shape (channel, display_name, status, error, reconnect_url) makes the output concrete. It is clearly a listing tool, distinguishable from siblings like channels_reconnect or channels_sync_settings, though it never explicitly contrasts itself with them.

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?

It gives a concrete when-to-use rule for `only_broken=true` (checking outages without listing healthy channels) and for `account_id` (one account in detail). It also gives a behavioral instruction for the error case — hand over `reconnect_url` rather than pointing at settings. It stops short of naming sibling tools as alternatives, so it is clear context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.