Skip to main content
Glama

Shager

by ai.shager
OverviewDiscussionsAdmin

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 or a Google Business Profile location (account_kind "location"; each location is its own channel). Only status ACTIVE accounts can receive posts; NEEDS_RECONNECT means the human must reconnect it. 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). Live: YouTube channels, X (Twitter) accounts, LinkedIn personal profiles, Bluesky accounts, Telegram channels and Mastodon accounts. Facebook: Awaiting Meta's approval: until then, only people we gave early access can connect. Pages only: Facebook lets no app publish to personal profiles. 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. TikTok: Pending TikTok's app review: until approved, posts can only go to private accounts and are published as private ("only me"). Privacy, interactions and commercial-content disclosure are chosen per post. TikTok takes no cover image and applies a chosen cover moment to public posts only, so Shager can put your cover image at the start of the video. 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. Pinterest: Awaiting Pinterest's approval: until then, only people we gave early access can connect. Business accounts only (switching is free on Pinterest). Each Pin is an image, a carousel of up to 5 images or a video, with a title, a description up to 800 characters and a link, on a board you pick for each account. No first comment, and comments can't be read through Shager. Impressions, saves and comments per Pin show up in Shager. You sign in on Pinterest's 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.

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",
-  "WHATSAPP"
-]New value: +[
+  "FACEBOOK",
+  "INSTAGRAM",
+  "LINKEDIN",
+  "TIKTOK",
+  "YOUTUBE",
+  "X",
+  "BLUESKY",
+  "TELEGRAM",
+  "MASTODON",
+  "THREADS",
+  "PINTEREST",
+  "GOOGLE_BUSINESS",
+  "WHATSAPP"
+]
  2. 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"
+]
  3. 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"
+]
  4. 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"
+]
  5. 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"
+]
  6. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial context beyond them: account status meanings, per-network approval gating, which networks are live vs awaiting approval, requires_media, caption limits, and fields like x_posts_this_month and tiktok.privacy_options. This is rich behavioral disclosure an agent could not get from the annotations.

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?

After a useful opening sentence, the description becomes a wall of per-network publishing rules (cover images, character limits, link clickability, approval statuses) that are largely irrelevant to invoking a list operation. The essential invocation information is buried and the structure is not front-loaded toward what an agent needs to call the tool.

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?

Given an output schema exists, return values needn't be explained, and the description errs on the side of over-supplying context. It is more than complete for calling the tool, though much of the detail pertains to downstream publishing rather than this list operation.

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% with the single enum (network) documented inline, so the schema already carries parameter meaning. The description adds no syntax or filtering detail beyond what the schema states, so the baseline 3 applies.

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 states a specific verb and resource (connected social accounts/channels of one workspace) and thoroughly defines what a channel is, including account_kind variants. It is clear enough to distinguish from most siblings, though it never explicitly contrasts with list_workspaces or get_structure, which also surface account/structure data.

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?

Usage is only implied: status semantics (ACTIVE can receive posts, NEEDS_RECONNECT requires human action) and per-network rules hint that this tool is the prerequisite for posting, but there is no explicit 'use this when…' or 'use X instead' routing. The agent must infer its role in the workflow.

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

All Shager toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources