Shager
Server Details
Schedule posts and videos to many social accounts at once, with a tracked link for each account.
TDQS
Scored across 70 tools
Most tools target a distinct resource+action (posts, channels, groups, media, webhooks, comments, team, auto-replies), and the descriptions explicitly steer between near-neighbours ('for a link inside a post use cta_url on create_post instead', 'use set_channel_status PAUSED instead of remove_channel'). The remaining friction is concentrated in the posting cluster (create_post without schedule_at = draft, schedule_post = time an existing draft, create_posts = bulk, validate_post = dry run), where an agent must read carefully to choose correctly.
Nearly everything follows a snake_case verb_noun pattern (list_posts, create_group, update_post, delete_comment, set_audience, revoke_approval), which makes scanning predictable. Minor deviations exist: whoami has no verb, complete_media_upload/create_media_upload are a two-phase pair, and retry_failed_accounts adds an adjective — all still readable.
70 tools is a very large surface even for a broad social-publishing platform spanning workspaces, channels, groups, posts, media, links, webhooks, analytics, comments, reviews, auto-replies and team management. Many tools genuinely earn their place, but the volume makes selection costly and several operations are split across near-duplicate endpoints rather than consolidated.
Coverage is unusually thorough: full CRUD for posts, groups, workspaces, webhooks and auto-replies, plus media upload, tracked links, analytics/insights, best times, holidays, comment moderation, approvals, team management and notifications. Gaps are small: no delete/update for tracked links, no media listing or deletion, and no read access to direct messages (only auto-reply activity).
Available Tools
70 toolsadd_post_noteAdd an internal note to a postAInspect
Adds a note for the team on a post, up to 5,000 characters: shown with the post in the app, never to the client reviewer and never published. get_approval lists the latest notes. Use it to explain a choice or leave your human a question.
Inputs: text (required), post_id (required), workspace_id (required), idempotency_key.
cancel_invitationCancel a team invitationADestructiveIdempotentInspect
Cancels an invitation that is still waiting for an answer (list_members invitations): its link stops working at once. Needs the publish scope and a key whose human manages the team, like invite_member. Removing a member or changing a role: remove_member and change_member_role, each after a manager's OK. (Not available in an unclaimed sandbox.)
Inputs: invitation_id (required).
cancel_postCancel a scheduled postADestructiveIdempotentInspect
Unschedules a post that has not started publishing, as the app's Cancel does: it goes back to APPROVED when the workspace requires approval or a reviewer approved it (schedule_post again, no new approval needed), otherwise to DRAFT.
Inputs: post_id (required), workspace_id (required).
change_member_roleChange a team member's roleADestructiveIdempotentInspect
Gives a team member (list_members) a new role and scope: manager (everything; with scope "all" also the team and plan), editor (writes and schedules posts, answers comments) or viewer (read only); scope "all" or workspace ids. It can hand out write access, so it first needs a manager's OK in Shager: the call answers needs_confirmation with confirm_url; after they approve, make the same call again. The owner's role never changes, a person can't change their own, and the team always keeps at least one manager with every workspace. Someone who stops being a full manager loses the API keys they created. (Not available in an unclaimed sandbox.)
Inputs: role (required), member_id (required), scope, confirmation_token.
complete_media_uploadFinish a local file upload (step 2 of 2)AIdempotentInspect
After the PUT to upload_url: checks that the stored file has exactly the declared size and type (otherwise the upload is dropped and you start again with create_media_upload), measures a video (width and height as displayed, duration_ms), and makes the media ready for create_post.media_ids. width, height and duration_ms are fallbacks, used only when a video can't be measured. Calling it again returns the same media.
Inputs: media_id (required), workspace_id (required), width, height, +1 more.
create_auto_replyCreate an auto-replyADestructiveInspect
Adds a rule that answers comments or direct messages automatically, on the person's behalf, from now on (never older comments). trigger COMMENT: when someone comments (optionally only with one of keywords, whole words, any case; only on post_ids; only on channel_ids), post one of public_replies (picked at random) under the comment and/or send message (+ link_url as a tracked short link) privately to the commenter, once per comment within 7 days. trigger MESSAGE: when someone sends a direct message (optionally with a keyword), answer with message within 24 hours. once_per_person (default true) answers each person once per rule per 30 days. At most 120 replies per account per hour. followers_only (COMMENT, Instagram): "comment a word, follow, get the link": the private reply asks them to follow and tap follow_button; the tap lets Shager check with Instagram, and only followers get message + link_url. attachment_media_id (Instagram, Facebook): also send a file privately (a guide, a price list, a coupon image); on comments it goes out after they tap follow_button, since the first private reply can only be text. It is saved paused (enabled=false) unless you pass enabled=true. An enabled rule answers real people with no one checking each answer, so enabled=true first needs your human's OK: the call answers needs_confirmation with confirm_url, where they read every text; after they approve, make the same call again. (Not available in an unclaimed sandbox.)
Inputs: name (required), trigger (required), workspace_id (required), enabled, +14 more.
create_connect_linkCreate a client connect linkCInspect
A link to send the account owner (your client or your human). They open it, sign in to the network and pick their accounts — no Shager account needed. The accounts then appear in list_channels. 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. (Not available in an unclaimed sandbox.)
Inputs: workspace_id (required), label, idempotency_key.
create_groupCreate an account groupAInspect
Create a group inside one workspace: a named set of its channels, so a post can target all of them at once. channel_ids must belong to this workspace. A group can have a market (audience_countries, audience_world, audience_timezone): its accounts without their own market are timed for it by get_best_times.
Inputs: name (required), workspace_id (required), channel_ids, audience_world, +3 more.
create_linkCreate a tracked linkAInspect
Makes a tracked short link for any web address, for a bio, a story, an email or an ad: each click is counted (list_links) and the visitor lands on the address with UTM tags added. Up to 100 new links a day per workspace. source and medium default to shager and link, campaign to none; words become lower-case-with-dashes. For a link inside a post use cta_url on create_post instead: every account then gets its own link, tagged automatically. (Not available in an unclaimed sandbox.)
Inputs: url (required), workspace_id (required), medium, source, +2 more.
create_media_uploadUpload a local file (step 1 of 2)AInspect
For a file on your machine that has no public URL: reserves the space and returns media_id and a signed upload_url. PUT the file's raw bytes there with exactly the returned headers (content-type, content-length, if-none-match: *) within 30 minutes, then call complete_media_upload with the media_id; until then the media can't go on a post. The file goes straight to Shager's storage, not through this API. Types: JPEG, PNG, WebP, GIF, MP4, MOV, WebM and PDF, up to 2 GB; size_bytes must be the file's exact size. For a file that is already online, upload_media_from_url does it in one call. A video file is deleted 7 days after the time of the posts that use it (a still stays); to post it again later, upload it again.
Inputs: file_name (required), mime_type (required), size_bytes (required), workspace_id (required).
create_pinterest_boardCreate a Pinterest boardADestructiveInspect
Creates a public board on a Pinterest account (name up to 50 characters) and returns it ({id, name, privacy}) for per_channel.pinterest_board_id. The board shows on the person's public Pinterest profile at once, so create one only when your human asked for it. At most 10 new boards an hour per account, and per person. (Not available in an unclaimed sandbox.)
Inputs: name (required), channel_id (required), workspace_id (required).
create_postCreate a postADestructiveInspect
One post, many accounts. Pick accounts with channel_ids and/or group_ids from one workspace; the post gets one destination per account, each with its own format, text override and network fields (per_channel). Without schedule_at the post is saved as a DRAFT and the response lists every validation issue (issues[]) so you can fix them with update_post; nothing is published. With schedule_at it is validated (all issues at once), checked against the key's caps and the X link allowance, and scheduled — then every account publishes at its own staggered time. Formats: default per network (Facebook/Instagram FEED, REEL with a video; YouTube SHORT; TikTok VIDEO; LinkedIn FEED, VIDEO with a video; X FEED). An unsupported format is an issue, never swapped silently. Links: cta_url becomes a tracked short link per account with UTM tags — in the caption where links are clickable (Facebook, LinkedIn, YouTube, Bluesky, Telegram, Mastodon) and in the first comment on Instagram. first_comment is a comment on Facebook/Instagram/YouTube and LinkedIn company Pages, a reply on X, Bluesky and Mastodon, and skipped on LinkedIn profiles, TikTok and Telegram. On X nothing is added automatically and any link you write (text or reply) costs one of the plan's monthly X link posts (whoami shows what is left). TikTok: per_channel.tiktok_privacy is required per account (values from list_channels); comments/duet/stitch default to off; set tiktok_commercial with brand_organic/brand_content for ads. YouTube: youtube_title/privacy/made_for_kids, overridable per channel. Time: schedule_at is ISO 8601 with an offset (2026-10-20T09:00:00+03:00); its exact UTC instant is preserved; the workspace timezone is for display. Staggering: accounts on one network go out one after another with a random stagger_min_seconds–stagger_max_seconds pause (default 30–90 s; Facebook and Instagram share a lane). Sends to more than 10 accounts or within 60 minutes need confirmation_token from the returned plan (you first get needs_confirmation with the plan). A different time per network, in the same post: schedule_at is the earliest send, and per_channel.delay_minutes moves an account later (Instagram 9:00, LinkedIn 12:00, X 18:00 = schedule_at 9:00, LinkedIn 180, X 540). get_post shows each account's send_at. Approval: if the workspace has approval_required, create the draft, request_approval, wait for get_approval to show approved, then schedule_post. Vary the caption per account — identical mass posts look like spam. With schedule_at the post goes out publicly on the person's real accounts at that time: only schedule what your human asked to publish.
Inputs: caption (required), workspace_id (required), poll, label, +65 more.
create_postsCreate many posts at onceADestructiveInspect
Up to 25 posts of one workspace in one call: a week or a month of content, or one piece per account at each account's best time (get_best_times next_times). Each item in posts is exactly a create_post body without workspace_id (channel_ids/group_ids, caption, media_ids, schedule_at, per_channel, fit_shape, confirmation_token…), and goes through create_post one by one, in order, with all its checks, caps and confirmations. One item's failure doesn't stop the others: results has one entry per item, in order, with ok and either the post or the error (code, message, details). An item that needs confirmation comes back with error.code needs_confirmation and its confirmation_token in error.details: show the plan to the human, then send only those items again with confirmation_token. validate_only: true runs validate_post on every item instead and saves nothing (each result is a validate_post answer with draft_id and confirmation_token). Retrying: give each item an idempotency_key, or one idempotency_key for the call (item i then uses ":"), and a retry replays the items that went through and retries the rest.
Inputs: posts (required), workspace_id (required), validate_only, idempotency_key.
create_webhookAdd a webhook endpointADestructiveInspect
Instead of polling get_post, have Shager POST events to your HTTPS endpoint (a CRM, your agent's server): post.destination.published (data: post_id, destination_id, channel_id, network, account, format, remote_url, remote_post_id, published_at, notice), post.destination.failed (… error, unconfirmed), post.completed (post_id, status, counts, destinations[] with state and remote_url), approval.decided (post_id, approval_id, decision, post_status, reviewer.name, comment). Body: { id, type, created_at, data } (data always has workspace_id). The id is the same on every retry: dedupe on it. Order is not guaranteed. Headers: Shager-Event-Id, Shager-Event-Type and Shager-Signature: t=,v1=<hex HMAC-SHA256 of "." with the secret>. Verify it on the raw body in constant time and refuse timestamps older than 5 minutes. Answer 2xx within 10 s. Anything else (redirects included) is retried: 6 attempts over about a day. An endpoint whose every attempt fails for 3 days is turned off; a successful send_test_webhook turns it back on. Signing secret (whsec_…): the REST API returns it once, in this response. Through an AI assistant or the CLI it is never returned (secret is null): the person copies a fresh one in the app (the workspace's Settings → webhooks → "New signing key") and puts it in the receiving system. https only; private, local and credentialed URLs are refused. Up to 10 endpoints per workspace. Publishing never waits for webhooks. (Not available in an unclaimed sandbox.)
Inputs: url (required), workspace_id (required), events, description.
create_workspaceCreate a workspaceAInspect
Create a workspace for a new client (agency) or brand. Its accounts are then connected inside it (create_connect_link). Its timezone is how schedule times without an offset are read and how dates are shown.
Inputs: name (required), timezone, idempotency_key, approval_required.
delete_auto_replyDelete an auto-replyADestructiveIdempotentInspect
Deletes a rule; it stops answering at once. Its activity stays in list_auto_reply_activity (kept 90 days).
Inputs: rule_id (required), workspace_id (required).
delete_commentDelete a commentADestructiveIdempotentInspect
Deletes a comment from the network for good. Instagram and Facebook Pages: any comment on the account's post. YouTube, X, LinkedIn company Pages, Bluesky and Mastodon: only the account's own comments and replies (hide others instead where hiding exists). Threads: not available (Shager doesn't hold Threads' delete permission). On X it is billed to the workspace's monthly X limit. Cannot be undone, so a person approves each deletion in Shager first: the first call answers needs_confirmation with confirm_url; after your human approves, make the same call again. (Not available in an unclaimed sandbox.)
Inputs: post_id (required), channel_id (required), comment_id (required), workspace_id (required), +1 more.
delete_groupDelete an account groupADestructiveIdempotentInspect
Deletes a group. Its accounts and posts stay; posts just stop remembering the group as a target. Cannot be undone through the API (create_group makes a new one).
Inputs: group_id (required), workspace_id (required).
delete_postDelete a draftADestructiveIdempotentInspect
Deletes a post that is not scheduled and never published (DRAFT, IN_REVIEW, CHANGES_REQUESTED, APPROVED, or a canceled post). A pending approval link stops working. Scheduled posts: cancel_post first. Published posts stay for their analytics. Cannot be undone through the API.
Inputs: post_id (required), workspace_id (required).
delete_webhookDelete a webhook endpointADestructiveIdempotentInspect
Stops sending events to this endpoint, including retries still pending. Cannot be undone.
Inputs: webhook_id (required), workspace_id (required).
get_analyticsHow posts are doingARead-onlyIdempotentInspect
How a workspace's posts did in a period: views, reach, likes, comments, shares, saves, engagement (likes + comments + shares + saves) and engagement rate, clicks on Shager's tracked links, and followers — in total, compared with the previous period of the same length, day by day, by network, by account, and the top posts. Numbers come from each network's own API and refresh every few hours (often in a post's first day, then less). A post counts in the period it was published in, with its latest numbers. Totals add up what the networks report: Facebook views appear once Meta approves read_insights, LinkedIn shares numbers only for company Pages (impressions as views, unique impressions as reach, likes, comments, shares; followers) and none for personal profiles, and a TikTok account counts only after it is reconnected with the video-reading permission and only for its public videos (otherwise by_network.measured=false, coverage.notes) — only their link clicks count. get_post shows one post per account, with null for a number the network doesn't report. Google Business Profile locations have no post numbers; business_profiles gives each location's profile views, calls, website clicks and direction requests for the period, read live from Google. Use it to answer 'what worked this week', to pick the best time or format, or to report to a client. Filter with channel_ids or group_ids.
Inputs: workspace_id (required), to, top, from, +2 more.
get_approvalGet the approval state of a postBRead-onlyIdempotentInspect
The latest approval request for a post: decision (PENDING, APPROVED or CHANGES_REQUESTED; the reviewer page offers only those two, so REJECTED never appears), the reviewer, when it was opened and decided, the reviewer's comment, and the team's internal notes on the post (add_post_note; the reviewer never sees them).
Inputs: post_id (required), workspace_id (required).
get_best_timesBest times to postARead-onlyIdempotentInspect
The best hours of the week to post, for each account of a workspace, with the next times they come round (ready for schedule_at). Each account is timed for its own audience: one country, several, the whole world, or a time zone — from this request (countries, world, timezone), else the account's market, else its groups' markets together (set_audience), else where its clicks come from, else the workspace's zone; audience says which and how each country is weighed. One market is read on its own clock; several markets on UTC, with each hour also given in every market's local time, so a worldwide group gets the hours that reach most of its audience. A worldwide audience with no clicks yet is weighed by an assumed mix (audience.assumed_mix). Every source Shager has comes back, most specific first, and best is the first with enough data: account_posts (the account's own posts of the last year, scored by likes, comments, shares, saves and clicks against its typical post; needs 12 measured posts), audience_clicks (when its audience clicked the posts' short links; 50 clicks, else workspace_clicks), shager_country (when people in each of its countries click Shager short links across all customers: counts per hour only, a country only above 500 clicks from 5 workspaces in 90 days), and study (Buffer's 2026 study of millions of posts per network, read in each market's local time; none for Pinterest, Bluesky, Telegram, Mastodon or Google Business). missing says why a more specific source wasn't used. To post at each account's best time without picking it yourself, give create_post, create_posts or schedule_post schedule_at "best": Shager picks every account's next free best time (one post, a delay per account) and says what it picked in best_time.
Inputs: workspace_id (required), world, format, timezone, +3 more.
get_claim_linkGet a fresh claim linkADestructiveInspect
Sandbox only. Issues a new claim link for your human (the one from signup stops working) and emails it again to contact_email when there is one, at most once a day per address (emailed says whether it went). Call it when you lost the signup response.
Inputs: no named parameters.
get_client_reportGet the client report linkAIdempotentInspect
The workspace's monthly report as a link anyone can open without a Shager account: its logo and name, posts, views, reach, engagement, clicks, followers, each network and the top posts for one month, ready to print or save as PDF. Made the first time it's asked for. Last month by default; add ?m=YYYY-MM for another month (month_url_template). Give it to a client or a business owner, or have Shager email it on the 1st of each month with set_client_report.
Inputs: workspace_id (required).
get_holidaysHolidays and posting guidanceARead-onlyIdempotentInspect
Holidays of every major tradition (Jewish/Israeli, Muslim, Christian, Orthodox, Druze, Bahá'í, Hindu, Buddhist, Sikh, Jain, Chinese, Persian, international and commercial days) with advice per day: avoid (no promotional posts to that audience), sensitive (respectful only), opportunity (greeting or themed post), normal. It helps when picking a date for an audience, since a promotional post on a day of mourning or fasting reads badly: the traditions to look at are the ones of each account's audience.
Inputs: to, from, language, traditions.
get_insightsWhat workedARead-onlyIdempotentInspect
What went with each account's better and worse posts, as findings to act on in the next post: video or photo, text alone, carousels, a question in the first line, a link, short or long text, 4+ hashtags, an emoji up front, weekends, and the format when it used several. Each finding gives the trait, better or worse, lift (its posts' typical result against the others', 2 = twice as good), how many posts are on each side, and advice in plain words. Also trend (the last 5 posts against the ones before: rising, falling or steady) and top_posts. Posts are scored against the account's own typical post by likes, comments, shares, saves and clicks on Shager's short links (views where a network gives nothing else), so findings are the account's, not an average of strangers. Needs 8 measured posts; a finding needs 3 posts on each side and a 25% difference. missing says what's short. These go together with results, they don't prove cause: try a finding and check again. Use it before writing the next posts; get_analytics has the numbers, get_best_times the hours.
Inputs: workspace_id (required), days, group_ids, channel_ids.
get_network_featuresWhat works on each networkARead-onlyIdempotentInspect
The feature × network table the site shows on /networks, built from the same code: for each kind of account (Facebook Page or profile, Instagram, Threads, YouTube, X, LinkedIn profile or company Page, TikTok, Bluesky, Telegram, Mastodon, Pinterest, Tumblr, Google Business Profile) whether it is open to everyone today, publishes automatically, takes a first comment and a video cover, lets you read, answer, hide and delete comments, runs auto-replies and private messages, reports post numbers, and whether removing it in Shager also cancels access at the network. value: yes, limited (see note), later (built, waiting for the network's approval of Shager), no (the network doesn't allow it). Check it before promising a feature to a person.
Inputs: language.
get_postGet a postARead-onlyIdempotentInspect
Status of a post and of every account it goes to: state, dispatch and publish time, live URL or error, and once published its results (views, likes, comments, shares, saves, link clicks; null = not reported by that network) — plus the remaining validation issues while it is still a draft, and next_steps.
Inputs: post_id (required), workspace_id (required).
get_structureSee the whole account: clients, accounts and groupsARead-onlyIdempotentInspect
How a Shager account is organized:
Organization: the whole account, with one plan and one team. Your key belongs to exactly one organization.
Workspaces: inside the organization. In the app a workspace is called a client when the organization is an agency (one workspace per client business) and a brand or simply "my accounts" when a person or business posts for itself (usually one workspace). Everything below lives inside one workspace and never crosses into another.
Channels: the connected social accounts of that workspace — one Facebook Page, one Instagram account, one YouTube channel, one X account, one LinkedIn profile or company Page, one TikTok account, one Bluesky account, one Telegram channel, one Mastodon account, one Threads profile, one Pinterest business account, one Tumblr blog, one Google Business Profile location each. A channel belongs to exactly one workspace.
Groups: named sets of that workspace's channels (for example "Hebrew pages" or "North branches"). A channel can be in several groups or in none. Targeting a group posts to all of its ACTIVE channels.
Media, posts, tracked links, webhooks and the client-approval setting also belong to the workspace.
A post belongs to one workspace and targets channel_ids and/or group_ids from that same workspace. Call get_structure (GET /structure) to see the whole tree in one call: every workspace with its channels and groups. When you talk to the person, use their words: "client" (agency) or "your accounts" (one business), and "group".
Returns the organization, then every workspace (client or brand) with its connected channels and its groups (each group lists its channel_ids; each channel lists the groups it is in). Use it before posting to pick the right workspace, channel_ids and group_ids.
Inputs: no named parameters.
hide_commentHide or show a commentADestructiveIdempotentInspect
Hides a comment from everyone but the account (hidden=true), or shows it again (hidden=false). Changes what the public sees: act on your human's request. Works on YouTube, Facebook Pages, Instagram and Threads only (list_comments can_hide); the account's own comments can't be hidden. X, LinkedIn, Bluesky and Mastodon offer no hiding to Shager: use delete_comment on the account's own replies instead. (Not available in an unclaimed sandbox.)
Inputs: post_id (required), channel_id (required), comment_id (required), workspace_id (required), +1 more.
invite_memberInvite someone to the teamADestructiveInspect
Emails a person an invitation to join this organization's team as a viewer (read only), for every workspace (scope "all") or only some (workspace ids from list_workspaces). The invitation link works for 7 days; inviting an address that already has an open invitation updates and resends it. Sends email to a person, so it needs the publish scope and a key whose human manages the team. Agents can't invite editors or managers, so a misled agent can't hand someone write access: the human does that in the app (Team page). At most 30 invitation emails per organization per day. (Not available in an unclaimed sandbox.)
Inputs: email (required), role, scope.
list_auto_repliesList auto-repliesBRead-onlyIdempotentInspect
The workspace's automatic-reply rules, oldest first — the first enabled rule that matches a comment or direct message answers it — each with its last-30-days numbers, plus what every account can do right now: comments (public replies, a private message to the commenter) and direct messages; missing_permissions are granted by reconnecting the account, or once the network approves Shager. What each network allows: Instagram: comments, public replies, private replies to the commenter, direct messages and files in private messages (an image, a video or a PDF); followers_only rules check who follows (works once Meta approves Shager; Instagram is in Meta's review). Facebook Pages: comments, public replies, private replies to the commenter, direct messages and files in private messages (an image, a video or a PDF); comments are read every 5 minutes until Meta delivers them instantly (works once Meta approves Shager's Page permissions; Facebook is in Meta's review). X: comments, public replies, private replies to the commenter and direct messages; billed to the workspace's monthly X limit (set_x_budget). YouTube: comments and public replies. LinkedIn company Pages: comments and public replies; Page comments are checked every 2 hours; LinkedIn has no messaging for Pages (works once LinkedIn approves Shager for company Pages). Not available: LinkedIn profiles, TikTok, Pinterest, Tumblr, Bluesky, Mastodon, Threads, Telegram, and Google reviews (Google requires the owner's consent for each reply).
Inputs: workspace_id (required).
list_auto_reply_activityAuto-reply activityARead-onlyIdempotentInspect
The latest comments and direct messages that reached the workspace's auto-replies, newest first: who wrote what, which rule answered, the public reply and private message sent, or why nothing was sent (status SENT, SKIPPED, FAILED or PENDING). Comments no rule was meant for are left out. Kept 90 days.
Inputs: workspace_id (required), limit, status, rule_id.
list_channelsList connected accountsBRead-onlyIdempotentInspect
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.
Inputs: workspace_id (required), network. Returns: items, next_cursor
list_commentsComments on a published postAInspect
Reads the comments (newest first, each with its replies) on a post Shager published, on one account. YouTube: comments and their replies; reply; hide others' comments; delete only the account's own. Facebook Pages: comments and their replies, once the Page granted Meta's comment permissions (pages_read_user_content, pages_manage_engagement; a Page connected before Shager asked for them needs a reconnect); reply; hide others' comments; delete any comment on the account's post. Instagram: comments and their replies; reply; hide others' comments; delete any comment on the account's post. X: replies from the last 7 days, up to 20 a read; every read, reply and delete is billed to the workspace's monthly X limit; reply; no hiding; delete only the account's own. LinkedIn company Pages: comments and their replies, answered as the Page; commenters come without names; reply; no hiding; delete only the account's own. Bluesky: replies two levels deep; reply; no hiding; delete only the account's own. Mastodon: replies, including followers-only ones the account can see, answered with the same visibility; reply; no hiding; delete only the account's own. Threads: the whole conversation under the post, once the profile granted threads_read_replies; reply; hide others' comments; no deleting. LinkedIn profiles, TikTok and Pinterest don't let apps manage comments; Telegram channel comments and Tumblr replies aren't offered; Google Business Profile reviews are read with list_reviews. Each comment carries can_hide and can_delete for this account. Read live from the network, never stored. Use it to answer questions, spot spam, or draft replies for a human to approve.
Inputs: post_id (required), channel_id (required), workspace_id (required).
list_connect_linksList client connect linksARead-onlyIdempotentInspect
The workspace's connect links that still work (not revoked, not expired): who each is for (label), its url to send again, when it expires (14 days after it was made), when it was last used and how many accounts were connected through it. revoke_connect_link stops one at once. (Not available in an unclaimed sandbox.)
Inputs: workspace_id (required). Returns: items, next_cursor
list_groupsList account groupsBRead-onlyIdempotentInspect
Groups of one workspace: named sets of its channels (by region, language, branch, campaign…). A channel can be in several groups or none, and a group never includes another workspace's channels. Target a group in create_post with group_ids to post to all its ACTIVE channels.
Inputs: workspace_id (required). Returns: items, next_cursor
list_linksTracked links and their clicksARead-onlyIdempotentInspect
The workspace's tracked short links, newest first (up to 200): each with its short_url, the original URL, its UTM tags, its clicks, when it was made, and the post and account it belongs to (null for links made by hand or with create_link; auto-reply links carry utm_medium auto-reply). Also the totals for the workspace (clicks and unique visitors, bots left out) and clicks by utm_source (unlabeled = links without a source of their own). For clicks per post, account and network in a period, use get_analytics.
Inputs: workspace_id (required), limit.
list_membersList team membersARead-onlyIdempotentInspect
The people on this organization's team and the invitations still waiting for an answer. role: manager (everything; with scope "all" also the team and plan), editor (writes and schedules posts, answers comments; doesn't connect accounts or change settings) or viewer (read only). scope: "all" (every workspace, including ones added later) or the workspace ids they can open. owner: the team's owner, whose role never changes. Agents can invite viewers (invite_member), resend viewer invitations and cancel invitations; removing members and changing roles (remove_member, change_member_role) need a manager's OK in Shager first.
Inputs: no named parameters.
list_notificationsList notificationsARead-onlyIdempotentInspect
What happened lately that the humans were told about (in the app and by email): posts that failed (fully or on some accounts, or only their first comment), accounts that need reconnecting, the X monthly limit reached, auto-reply rules failing repeatedly, accounts a client connected through a connect link, approvals given or changes requested, team members who joined, and posts waiting for the human to share them on a personal Facebook profile (post_handoff, with the share link). Newest first. Each item has a type, an English title and text, the facts in payload, and the app link. Useful to check on posts after scheduling them, or to tell the human what needs them.
Inputs: type, limit, since, workspace_id. Returns: items, next_cursor
list_postsList postsARead-onlyIdempotentInspect
Posts in a workspace, newest first, with cursor pagination: pass next_cursor as cursor. Filters combine: status, network, channel_id (one account), group_id (posts to any account in that group), query (words in the caption or internal label), and from/to on the scheduled time. Date-only from/to filters use inclusive UTC days, not workspace-local days. Offset timestamps filter exact instants. Posts without a date (unscheduled drafts) only appear without from/to.
Inputs: workspace_id (required), to, from, limit, +6 more. Returns: items, next_cursor
list_reviewsRead Google reviewsARead-onlyIdempotentInspect
The reviews of one Google Business Profile location (a list_channels account with network GOOGLE_BUSINESS): each review's stars (1–5), text, author, dates and the owner's reply, plus the average rating and the total count. Read live from Google (refresh: true skips Shager's short cache), at most 30 reads per 10 minutes per location and per person. Read only: Google requires the owner's express consent for automated replies, so a person answers reviews on Shager's Comments page, never an agent. reviews is null with a note when Google couldn't be asked.
Inputs: channel_id (required), workspace_id (required), refresh.
list_webhooksList webhook endpointsBRead-onlyIdempotentInspect
The workspace's webhook endpoints: URL, events, whether it is on (and why it was turned off), the secret's last 4 characters, and the last delivery attempt (time, event type, HTTP status, error).
Inputs: workspace_id (required). Returns: items, next_cursor
list_workspacesList workspacesARead-onlyIdempotentInspect
A workspace is what the app calls a client (for an agency) or a brand (for a person or business posting for itself; usually just one). Its connected accounts (channels), groups, media, posts and tracked links live in it and never cross into another workspace. approval_required means a client reviewer must approve each post before it can be scheduled (request_approval). For every workspace with its channels and groups in one call, use get_structure.
Inputs: no named parameters. Returns: items, next_cursor
mark_notifications_readMark notifications as readAIdempotentInspect
Marks every notification as read for your human (the bell in the app goes to zero), for example after you told them what needed them. It changes nothing else.
Inputs: no named parameters.
move_channelMove an account to another workspaceADestructiveInspect
Moves a connected account, with its connection, to another workspace (client or brand) of this organization: nobody signs in again. It leaves the old workspace's groups. Posts already made for it stay in the old workspace (published ones keep their numbers there); posts there that haven't gone out won't go to it any more. The answer gives its channel_id in the new workspace (a new id when the old workspace keeps its history). It changes which client an account belongs to: confirm with your human first. (Not available in an unclaimed sandbox.)
Inputs: channel_id (required), workspace_id (required), target_workspace_id (required).
remove_channelRemove (disconnect) an accountADestructiveIdempotentInspect
Disconnects an account from the workspace: Shager deletes its keys for the account (and, where the network offers it, cancels Shager's access there; see get_network_features revoke). Posts already published keep their numbers; posts waiting to go out won't go to it. Only the account's owner can connect it again (create_connect_link), so this first needs a manager's OK in Shager: the call answers needs_confirmation with confirm_url; after they approve, make the same call again. To stop posting for a while without losing the connection, use set_channel_status PAUSED instead. (Not available in an unclaimed sandbox.)
Inputs: channel_id (required), workspace_id (required), confirmation_token.
remove_memberRemove someone from the teamADestructiveIdempotentInspect
Removes a team member (list_members): they lose access at once, and the API keys they created here stop working. It first needs a manager's OK in Shager: the call answers needs_confirmation with confirm_url; after they approve, make the same call again. The owner can't be removed, nobody removes themselves this way, and the last full manager stays. (Not available in an unclaimed sandbox.)
Inputs: member_id (required), confirmation_token.
reply_to_commentReply to a commentADestructiveInspect
Publishes a reply, as the account, to a comment on a post Shager published (YouTube, Facebook Pages, Instagram, X, LinkedIn company Pages, Bluesky, Mastodon and Threads). It is public at once and can't be unsent, so a person approves each reply in Shager first: the first call answers needs_confirmation with confirm_url, where your human sees the comment and your exact text; after they approve, make the same call again and it goes out. Up to 2,200 characters, within the network's own limit (Bluesky 300, Threads 500, Mastodon the server's). On X the reply is billed to the workspace's monthly X limit. delete_comment can remove it again except on Threads. (Not available in an unclaimed sandbox.)
Inputs: text (required), post_id (required), channel_id (required), comment_id (required), +2 more.
request_approvalSend a post for client approvalADestructiveInspect
The approval flow: a client reviewer (not a Shager user) gets a link, opens it on their phone without logging in, sees the post per account and approves it or asks for changes (with a comment). The post moves to IN_REVIEW; get_approval shows the decision (APPROVED or CHANGES_REQUESTED); revoke_approval takes the link back while it is pending; an APPROVED post can be scheduled as long as its content is unchanged. An approval requested by an agent never schedules the post by itself, even when it has a date: once get_approval shows APPROVED, call schedule_post. Returns the link to send (and a WhatsApp link when the reviewer has a phone); send_email emails it. When the workspace has approval_required, Shager emails the link to the reviewer itself (reviewer_email and send_email: true are required) and the link is not returned, so the agent can't approve its own post. Useful anyway when a human should look first. (Not available in an unclaimed sandbox.)
Inputs: post_id (required), workspace_id (required), reviewer_name (required), send_email, +3 more.
resend_invitationSend a team invitation againADestructiveInspect
Emails a waiting viewer invitation again, with 7 more days to accept. Invitations for editors or managers are resent by a person in the app, so an agent can't revive write access someone let lapse. At most once a minute per invitation, and within the 30 invitation emails per organization per day. Sends email to a person: publish scope and a key whose human manages the team. (Not available in an unclaimed sandbox.)
Inputs: invitation_id (required).
retry_failed_accountsRetry the accounts a post failed onADestructiveInspect
Sends a FAILED or PARTIALLY_PUBLISHED post again, right now, to the accounts it failed on; accounts it already reached are left alone. Fix the cause first (get_post shows each account's error; often the human must reconnect the account): disconnected or paused accounts stay failed, and an account whose outcome is unknown (the network may have published it) is never retried, so nothing is posted twice. The content is unchanged, so an approval still holds; the plan's monthly limits apply as for scheduling. It goes out publicly at once: retry only when your human wants it. (Not available in an unclaimed sandbox.)
Inputs: post_id (required), workspace_id (required).
revoke_approvalTake back an approval linkADestructiveIdempotentInspect
Revokes the post's pending approval link (the reviewer can't open it any more) and moves an IN_REVIEW post back to DRAFT. A decision already made stays as it is. Send a new link with request_approval.
Inputs: post_id (required), workspace_id (required).
revoke_connect_linkRevoke a client connect linkADestructiveIdempotentInspect
Stops a connect link at once: nobody can connect accounts through it any more. Accounts already connected through it stay connected.
Inputs: link_id (required), workspace_id (required).
rotate_webhook_secretReplace a webhook's signing secretADestructiveInspect
Makes a new signing secret for a webhook endpoint and returns it once (store it now): deliveries from now on are signed with it, and the old secret stops working at once, so update the receiving side right away. Use it when the old secret may have leaked.
Inputs: webhook_id (required), workspace_id (required).
schedule_postSchedule a postADestructiveInspect
Give an existing draft (or approved post) a time. The post is validated for every account (all issues at once), checked against the key's caps and the X link allowance, and — when the workspace requires approval — must be APPROVED with unchanged content. schedule_at is ISO 8601 with an offset; the workspace timezone is used for display. Each account then publishes at its own staggered time (stagger_min/max_seconds on the post), plus its per_channel.delay_minutes when the post gives a network a later time. More than 10 accounts or a start within 60 minutes needs confirmation_token from the returned plan: without it you get needs_confirmation and details.plan (accounts by network, first and estimated last dispatch, X link-post cost, TikTok notes) to show your human. The post then goes out publicly on the person's real accounts: only schedule when your human asked to publish it. Scheduling needs the publish scope and a claimed sandbox. To move a scheduled post, call schedule_post again with the new time; cancel_post stops it.
Inputs: post_id (required), schedule_at (required), workspace_id (required), confirm, +2 more.
send_test_webhookSend a test webhook eventAInspect
Sends a signed webhook.test event to the endpoint now and returns what happened (delivered, HTTP status, error, time taken). Tried once, no retries. A turned-off endpoint that answers 2xx is turned back on. (Not available in an unclaimed sandbox.)
Inputs: webhook_id (required), workspace_id (required).
set_audienceSet who accounts speak toAIdempotentInspect
Set the market of accounts or groups: the countries they speak to, the whole world, and/or one time zone. get_best_times times each account for its market (an account's own wins over its groups'; an account in several groups gets all their countries). Use it when a workspace's accounts or groups serve different markets, e.g. one group for the US and one for Israel, or a group for everyone. clear: true removes the market, so Shager goes back to where the clicks come from.
Inputs: workspace_id (required), clear, world, timezone, +3 more.
set_channel_statusPause or resume an accountADestructiveIdempotentInspect
Pauses an account (PAUSED: its connection is kept, nothing new can be scheduled to it, and a post due while it is paused fails for that account, with the reason in get_post) or turns it back on (ACTIVE). Resuming needs a working connection (a NEEDS_RECONNECT account is reconnected by the human, e.g. with create_connect_link) and room in the plan's account allowance. To disconnect an account for good, use remove_channel (it needs a manager's OK).
Inputs: status (required), channel_id (required), workspace_id (required).
set_client_reportSet who gets the client reportADestructiveIdempotentInspect
Who gets the monthly report by email (up to 10 addresses; [] stops the emails), its language, and/or a new link. Each recipient gets the link for the month that just ended on the 1st, from 08:00 in the workspace's time zone, with a link to stop getting it. regenerate: true makes a new link and the old one stops working at once: use it when the link reached someone it shouldn't. Shager then emails these people every month on its own, so it needs the publish scope and a claimed organization: only add addresses your human asked for (the client's own, or theirs). (Not available in an unclaimed sandbox.)
Inputs: workspace_id (required), lang, recipients, regenerate.
set_x_budgetSet the monthly X spending limitADestructiveIdempotentInspect
X bills Shager for every read, reply and DM. This sets the most, in US dollars, that this workspace may use on X per calendar month (UTC) for comments and auto-replies; 0 turns X comments and auto-replies off. Default 5. Lowering it takes effect at once. Raising it spends the customer's money, so a workspace manager approves it in Shager first: the first call answers needs_confirmation with confirm_url; after they approve, make the same call again. (Not available in an unclaimed sandbox.)
Inputs: workspace_id (required), monthly_limit_usd (required), confirmation_token.
test_auto_replyTry an auto-reply without sendingARead-onlyIdempotentInspect
A dry run: given a comment or direct message text (and optionally the account and the Shager post it's on), says which rule would answer it, first enabled match wins, oldest first, and exactly what would go out (public reply options, private message, link, file, the button step), and whether that account can send each part. Nothing is sent or recorded. Use it to check keywords and texts before asking your human to turn a rule on. Paused rules that would match are listed too.
Inputs: text (required), trigger (required), workspace_id (required), post_id, +1 more.
update_auto_replyChange an auto-replyADestructiveIdempotentInspect
Changes a rule: send only the fields to change. enabled=false pauses it at once. Turning a rule on, or changing what an enabled rule sends or where, first needs your human's OK in Shager, as in create_auto_reply (needs_confirmation with confirm_url, then the same call again). (Not available in an unclaimed sandbox.)
Inputs: rule_id (required), workspace_id (required), name, enabled, +14 more.
update_groupChange an account groupADestructiveIdempotentInspect
Renames a group and/or replaces its accounts (channel_ids becomes the whole list; [] empties it). channel_ids must belong to this workspace. Posts already made keep the accounts they had. Its market is set with set_audience.
Inputs: group_id (required), workspace_id (required), name, channel_ids.
update_postUpdate a draftADestructiveIdempotentInspect
Change any field of a post that is not scheduled or published (DRAFT, IN_REVIEW, CHANGES_REQUESTED, APPROVED). Send only the fields to change; channel_ids/group_ids replace the account list, per_channel entries are merged field by field into each named account's overrides, media_ids replace the media. Use null to clear cta_url, cta_text, first_comment, label, campaign, cover_media_id, tiktok_cover_ms, cover_first_frame, or a per_channel caption/first_comment override; an empty first_comment suppresses inheritance for that account. Changing content after a client approval sends the post back to DRAFT (approve again). A SCHEDULED post must be cancel_post-ed first. The response lists the remaining issues.
Inputs: post_id (required), workspace_id (required), poll, label, +62 more.
update_workspaceChange a workspace's settingsADestructiveIdempotentInspect
Renames a workspace, changes its time zone (how dates are shown and how times without an offset are read; scheduled posts keep their exact instant), and/or its default UTM tags for tracked links (utm_source, utm_medium, utm_campaign; an empty string goes back to Shager's automatic value). Send only what changes. approval_required can't be changed here on purpose: it is the client's safeguard, so a manager turns it on or off in the workspace's Settings in the app.
Inputs: workspace_id (required), name, timezone, utm_medium, +2 more.
upload_media_from_urlUpload media from a URLAInspect
Downloads a public image (JPEG, PNG, WebP, GIF), video (MP4, MOV, WebM) or PDF into the workspace and returns a media id to put in create_post.media_ids. Media is per workspace and reusable across posts, except that a video file is deleted 7 days after the time of the posts that use it (a still stays): to post it again later, upload it again. Shager measures every video itself: width and height as displayed (a rotated phone video counts as portrait) and duration_ms come back in the response, and validate_post checks Reels, Shorts, Stories and TikTok length and shape rules with them (Shorts: vertical or square, up to 3 minutes; Instagram Reels 3 s–15 min; Stories up to 60 s). A file that doesn't fit a network needn't be re-made: set fit_shape and/or fit_length on the post and Shager makes a fitting copy for each network (validate_post lists them in fits). width, height and duration_ms are optional and only used when a file can't be measured; measured values win. A video that comes back with null width, height or duration_ms couldn't be measured: pass them and upload again before scheduling it. Private, local and credentialed URLs are refused. Size limit: 2 GB.
Inputs: url (required), workspace_id (required), width, height, +3 more.
validate_postValidate a post (dry run)ARead-onlyIdempotentInspect
Checks a post against every account's network rules without saving anything and returns ALL issues at once. It approves nothing by itself: read next_step, which says in plain words what to do (fix issues, ask the human to confirm and pass confirmation_token, or create_post) (caption length, format support, media requirements, video length and shape, YouTube title, TikTok privacy and commercial fields, disconnected accounts). With schedule_at it also reports the X link allowance, the key's caps and whether the send would need confirmation_token from the returned plan, plus the dispatch plan. Run it before create_post when in doubt; it needs only the read scope and works in a sandbox.
Inputs: caption (required), workspace_id (required), poll, label, +63 more.
whoamiWho am IARead-onlyIdempotentInspect
Start here. The organization this key belongs to, its plan and usage (accounts and posts this month, X posts and X link posts left), whether the key may publish (scope, claimed sandbox and a plan in force; why_not says what is missing, and without publishing only drafts work), the key's caps, and — in a sandbox — the claim state. Use can_publish to decide between drafting and scheduling. app_only lists what only a person can do in the app, and why.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Schedule and publish social media posts to Facebook, X, LinkedIn, Instagram, Threads and more.
Schedule and publish social posts to Instagram, TikTok, X, LinkedIn, YouTube and five more networks.
Schedule and publish social media posts to Instagram, Facebook, TikTok, X, LinkedIn and more.
Schedule posts to Instagram, TikTok, LinkedIn, X and 6 more. Track analytics and reply to comments.
Related MCP Servers
AlicenseBqualityBmaintenanceSchedule, publish, and measure social posts on Facebook, Instagram, TikTok, LinkedIn, Threads, Pinterest, and X for one brand or many.38MIT- -
- AlicenseAqualityDmaintenanceAI-powered social media posting across 14 platforms. Post to Twitter, Instagram, TikTok, Facebook, LinkedIn, YouTube and more with one command. AI adapts content per platform, schedules posts, and generates 30-day content calendars.6MIT
- FlicenseAqualityCmaintenanceSchedule and manage social media posts across Facebook, Instagram, Twitter/X, LinkedIn, YouTube, TikTok, and Pinterest directly from Claude.10-
Glama MCP Gateway
Add one secure layer between your agents and this server.