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.

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

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.4/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds genuinely new behavior: a channel in 'error' is NOT receiving messages, reconnect_url opens the repair directly, and the agent must not fabricate a link or redirect the user to settings. That is operational and conversational context annotations cannot carry.

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?

Three tight paragraphs: row shape first, failure-handling instructions second, the outage shortcut last. Every sentence carries actionable content; no restatement of the title or boilerplate.

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?

5 optional parameters, no output schema, and the schema already defines the per-parameter return variations (e.g. account_id detail mode). The description covers the default list shape and the error path well, though it does not surface the account_id detail mode or chats pagination, leaving that entirely to the schema.

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 chats, account_id, chats_offset and in_workspace are fully documented in the schema. The description only restates only_broken's semantics and the reconnect_url return field, adding little parameter-level meaning beyond structured data — baseline 3.

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?

Names a specific verb and resource ('The messaging channels connected to this workspace') and immediately frames the row shape (channel, display_name, status, error, reconnect_url), which distinguishes it from siblings like channels_sync_settings, channels_contacts and channels_connect. An agent can tell what it returns without opening the schema.

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?

Gives concrete routing guidance for the outage case ('Pass only_broken=true to check for outages without listing the healthy channels') and prescribes the exact remediation flow when status is 'error'. It does not name sibling alternatives outright, but the when-to-use context for health checks is clear.

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.