Skip to main content
Glama

List connected accounts

list_channels
Read-onlyIdempotent

The connected social accounts (channels) of one workspace (client or brand). A channel is one social destination: a Facebook Page, an Instagram professional account, a YouTube channel, an X account, a LinkedIn profile, a LinkedIn company Page (account_kind "company"), a TikTok account, a Bluesky account, a Telegram channel, a Mastodon account (handle @name@server), a Threads profile, a Pinterest business account, a Tumblr blog (account_kind "blog"; each blog, side blogs included, is its own channel), a Google Business Profile location (account_kind "location"; each location is its own channel) or a personal Facebook profile (network FACEBOOK, account_kind "profile": Facebook lets no app post there, so nothing reaches the profile until the human posts it. At the post's time Shager emails them a share link: on a phone one tap opens Facebook with the files and the text copied, on a computer they download, copy and open Facebook. Facebook picks a profile video's thumbnail itself, so the post's cover image is offered on that page to upload by hand. get_post shows that account as state AWAITING_USER with share_url until they say they posted it (then PUBLISHED, with the link if they gave one) or SKIPPED if they chose not to; no first comment and no numbers for a profile). Only status ACTIVE accounts can receive posts; NEEDS_RECONNECT means the human must reconnect it, PAUSED that it was paused (set_channel_status resumes it). Disconnecting an account is left to the human in the app. Each row tells you the network's rules: formats, caption_limit, whether a first_comment exists (per account: LinkedIn company Pages yes, LinkedIn profiles no), whether links in the caption are clickable, requires_media, and paid_links (X: every post comes from the monthly allowance in x_posts_this_month, and a post with a link also from x_link_posts_this_month). TikTok rows carry tiktok.privacy_options — the only values allowed in per_channel.tiktok_privacy — or null with a note when TikTok could not be asked. Pinterest rows carry pinterest.boards ({id, name, privacy}) — per_channel.pinterest_board_id must be one of them — or null with a note (pinterest.reason "business": Pinterest refuses a non-business account's boards to apps, so the human must switch it to a business account and reconnect). YouTube rows carry youtube.playlists ({id, title}) for per_channel.youtube_playlist_id, or null with a note when YouTube could not be asked. Live: YouTube channels, X (Twitter) accounts, LinkedIn personal profiles, TikTok accounts, Bluesky accounts, Telegram channels, Mastodon accounts, Pinterest business accounts and Tumblr blogs. Facebook: Awaiting Meta's approval: until then, only people we gave early access can connect. Pages are published automatically. Facebook lets no app publish to personal profiles, so for a profile Shager gets the post ready at its time and emails you a link: one tap shares it from your phone, a few short steps from a computer. Nothing goes on the profile until you share it. On a profile Facebook picks the video's thumbnail itself, so your cover image waits on that page for you to upload by hand. A profile gets no first comment and no numbers. That works today, without waiting for Meta. Posts, photos, video, Reels and Stories, with your own cover image for videos. First comment with a clickable link. Instagram: Awaiting Meta's approval: until then, only people we gave early access can connect. Connected directly with Instagram Login or through a Facebook Page. Your own cover image for Reels. Links in captions and comments aren't clickable on Instagram: the tracked link goes in the first comment as text, and a clickable link can only go in the profile. Threads: Awaiting Meta's approval: until then, only people we gave early access can connect. Up to 500 characters (an emoji counts as several). Text, up to 20 images and videos in one carousel, or a video up to 5 minutes. Text posts can carry a link card, and any post can get a topic and a choice of who can reply. The first comment is posted as a reply, and replies, views and likes show up in Shager. You sign in on Threads' own screen and never give us your password. Google Business Profile: Awaiting Google's approval: until then, only people we gave early access can connect. Each location is its own profile, and you choose which locations to connect. A post is an update, an event or an offer, with up to 1,500 characters, one photo and a button such as Book, Order or Learn more. No video and no first comment. Reviews can be read and answered in Shager, by hand only, when you decide. Profile views, calls, website clicks and direction requests show up in Shager. You sign in on Google's own screen and never give us your password.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>"
    },
    "name": "list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoOnly accounts on this network.
workspace_idYesWorkspace id from list_workspaces

Output Schema

NameRequiredDescriptionDefault
itemsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "BLUESKY",
      -  "TELEGRAM",
      -  "MASTODON",
      -  "THREADS",
      -  "PINTEREST",
      -  "GOOGLE_BUSINESS",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "TELEGRAM",
      +  "MASTODON",
      +  "THREADS",
      +  "PINTEREST",
      +  "GOOGLE_BUSINESS",
      +  "TUMBLR",
      +  "WHATSAPP"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "BLUESKY",
      -  "TELEGRAM",
      -  "MASTODON",
      -  "THREADS",
      -  "PINTEREST",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "TELEGRAM",
      +  "MASTODON",
      +  "THREADS",
      +  "PINTEREST",
      +  "GOOGLE_BUSINESS",
      +  "WHATSAPP"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "BLUESKY",
      -  "TELEGRAM",
      -  "MASTODON",
      -  "THREADS",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "TELEGRAM",
      +  "MASTODON",
      +  "THREADS",
      +  "PINTEREST",
      +  "WHATSAPP"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "BLUESKY",
      -  "TELEGRAM",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "TELEGRAM",
      +  "MASTODON",
      +  "THREADS",
      +  "WHATSAPP"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "BLUESKY",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "TELEGRAM",
      +  "WHATSAPP"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / network / enum
      Previous value: -[
      -  "FACEBOOK",
      -  "INSTAGRAM",
      -  "LINKEDIN",
      -  "TIKTOK",
      -  "YOUTUBE",
      -  "X",
      -  "WHATSAPP"
      -]New value: +[
      +  "FACEBOOK",
      +  "INSTAGRAM",
      +  "LINKEDIN",
      +  "TIKTOK",
      +  "YOUTUBE",
      +  "X",
      +  "BLUESKY",
      +  "WHATSAPP"
      +]
  7. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior. The description usefully explains what the status values mean for downstream action (ACTIVE vs NEEDS_RECONNECT vs PAUSED) and that disconnection cannot be done via the API, but roughly two thirds of the text describes posting mechanics, per-network formatting and connection approvals that are irrelevant to a read-only listing call.

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 first sentence is well front-loaded, but the body is several hundred words of marketing and network-specific copy. The personal-Facebook-profile explanation appears twice almost verbatim, and long passages on TikTok, Pinterest and Google Business Profile approvals have no bearing on listing channels.

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?

This is a two-parameter read-only list tool with an output schema, so the description needs only scope, filter behavior and status semantics. Those are present but buried under a large volume of unrelated posting and connection-approval detail, which makes the definition noisy rather than complete.

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 coverage is 100% and both parameters are already documented with an enum and a max length, so the description adds little parameter-level meaning. It never explains how the network filter interacts with the workspace requirement or what happens for a network with no connected accounts.

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 sentence names the verb and resource precisely: connected social accounts (channels) of one workspace, and clarifies that a channel is a single social destination. It never names a sibling like list_workspaces as the alternative for a different scope, but the scope is unmistakable.

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

Usage Guidelines3/5

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

There is implicit guidance: only ACTIVE accounts can receive posts, NEEDS_RECONNECT requires human reconnection, PAUSED is resumed via set_channel_status, and disconnecting is left to the human in the app. However there is no explicit statement of when to call this versus list_workspaces or other listing tools, and most of the text is about posting rules rather than about when to list channels.

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.

Resources