OmniSocials
Server Details
Official OmniSocials MCP server — schedule and publish posts, stories, and reels across 11 platforms (Instagram, Facebook, LinkedIn, YouTube, TikTok, X, Pinterest, Bluesky, Threads, Mastodon, Google Business), plus media, analytics, hashtag sets, inbox, and webhooks.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 69 tools
Most tools map to a distinct resource and action, and detailed descriptions clarify close pairs such as get_post_analytics vs get_posts_analytics and list_inbox_conversations vs get_next_unanswered. However, get_post_status is explicitly redundant with get_post for agents, and create_and_publish_post overlaps create_post plus publish_post, so a few boundaries are blurred.
Names consistently use snake_case verb_noun phrasing such as list_posts, get_post, create_tag, update_webhook, and delete_media. Minor variations like create_and_publish_post and get_next_unanswered are still readable and follow the same convention.
69 tools is far beyond an agent-friendly surface and falls in the rubric's extreme-mismatch range of 50+. Although the social-media management domain is broad, the set is difficult to navigate as a whole and includes many niche administrative tools.
Coverage is broad across posting, media, analytics, inbox moderation, approvals, automations, tags/hashtags, webhooks, and workspaces. Remaining gaps are minor but real: approval workflows can only be listed, folders lack update/delete/get operations, and accounts lack connect/disconnect operations.
Available Tools
69 toolsapprove_postADestructiveInspect
Approve the current step of a post's approval workflow. Only works on a post with approval_status 'pending' (post status in_approval) — check get_post first. IMPORTANT: only succeeds if the connected user is a listed approver for the workflow's CURRENT step (steps approve in order); a forbidden error means the user isn't an approver for this step yet — tell them who needs to approve instead, don't retry. If this is the last step, the post is finalized immediately (moves to scheduled or posting). If steps remain, the post stays in_approval and the next step's approvers are notified. Pass step_order: the current_step that get_post_approval shows (the step the user reviewed). Then a repeated call, for example after a timeout, never approves the next step too: it answers step_changed with the step the review is on now. On step_changed, call get_post_approval again and ask the user before you decide on the new step.
Inputs: id (required), step_order.
check_media_compatibilityARead-onlyInspect
Check whether a video/image will be accepted by the platforms CONNECTED to this workspace, BEFORE uploading or posting. Use this when the user gives you a file (URL) so you can warn them upfront — e.g. "this 995 MB video won't post to Instagram (max 300 MB), continue?" — then confirm before uploading. Provide ONE of: a public 'url' (size/type read via HEAD), an existing 'media_id', or 'size_bytes' + 'mime'. For an image with a known size (a library file) the answer also has IMAGE FIT rows: per connected channel, whether its feed shows the image uncropped and what a post does by default (Instagram crops a 9:16 / wide image to 4:5 / 1.91:1 around the subject; Pinterest keeps a tall Pin and reports it). When a row says fits: false, ask the user "crop to (recommended for Instagram: Meta can boost it) or keep the original (the channel cuts it itself)?" and pass the answer as media_fit on create_post.
Inputs: url, mime, media_id, size_bytes.
create_and_publish_postADestructiveInspect
Create a new post and publish it immediately (no scheduling). Same media rules, channel IDs, and workspace selection rule as create_post apply (only one workspace → use it; multiple workspaces with no named one → ask first; named workspace → use and remember; mention workspace name on success). linkedin (personal profile) and linkedin_page (company page) are independent channels.
Pinterest board (auto-default to first board): If Pinterest is in channels and pinterest.board_id is NOT provided, do NOT block on asking — and do NOT skip Pinterest. Call get_account on the Pinterest account, take the FIRST board from the returned boards list, and pass its id as pinterest.board_id. In your reply, mention which board you used (e.g. "Published to your 'Marketing' board on Pinterest — let me know if you'd prefer a different one.") so the user can redirect. If the user named a specific board in the request, match it (case-insensitive) against the list and use that one instead.
X threads: For a chained X thread, pass x.thread_parts (2–25 { text } parts, each <= 280 chars). Do NOT split into "1/", "2/" inside content — that posts a single tweet, not a thread.
X posts containing a link: X treats a post whose text contains a link written with http:// or https:// as a link post (a bare domain or a www. link does not count). Link posts on X are a feature the organisation enables on its OmniSocials account. When it is not enabled, the request is refused up front with an x_feature_not_enabled error, or the X target alone fails while the other platforms still publish: tell the user, offer to post without the link or without X, and do not retry as is. Never remove a user's link without asking them.
Inputs: content (required), x, tags, type, +30 more.
create_automationAInspect
Create a comment-to-DM automation on the connected Instagram account (default), on the connected Facebook Page (platform 'facebook') or on the connected X account (platform 'x'): when somebody comments one of the keywords on the post (or sends it in a DM, or in an Instagram story reply, see triggers), the account DMs them dm_text once, and optionally posts one of public_replies under the comment. On Facebook the DM lands in Messenger. Before creating one, show the user the keyword(s) and the exact DM text and get a yes: the DM goes out in their name. Meta rules, the same on Instagram and Facebook: one private reply per comment, within 7 days of the comment; an automatic message only within 24 hours after the person's last DM, button tap or quick reply (a comment does not open that window); OmniSocials caps sends at 700 DMs an hour per account and platform, and an answer over the cap waits in a queue and goes out as soon as there is room (for up to about a day). For scope 'post' pass one of post_id (an OmniSocials post, scheduled or live), instagram_media_id (an Instagram post published outside OmniSocials) or facebook_post_id (a Page post published outside OmniSocials). On X the automation answers DMs only: triggers ['dm'] (the default there; X allows an automated DM only after the person wrote first), so a DM to the X account with a keyword, or any first message with match 'any', gets dm_text once per person; no post fields and no public replies. An X automation runs only while X DMs are turned on for the workspace in OmniSocials (Social Inbox, X DMs card, or the automation editor): an active create without them answers 409 x_dms_off, so tell the user where to turn them on, or create it with status 'paused'. 409 x_not_connected means the workspace has no X account. Every X answer ends with the line 'Reply STOP to stop automatic messages.', and a person who replies STOP gets no automatic DM from that X account again (the stop list belongs to the account: it holds after the automation is deleted, for later automations and in every workspace with that account). X takes at most 15 answers per 15 minutes and 450 a day per account; more wait in the queue for up to an hour. X does not give apps the messages of an encrypted X Chat conversation, so those get no answer. Follow first (follow_gate true, Instagram only): the link in dm_text goes out only to people who follow the account. On a comment the private reply is a short first message with one button; the tap makes OmniSocials ask Instagram whether the person follows: a follower gets dm_text, anybody else gets not_following_text with a button to tap again after following (a DM or story reply trigger checks at once). Texts hold 640 characters and buttons 20; leave them out for the defaults, and show the user the texts before creating it. Facebook and X have no follow status (400 follow_gate_instagram_only). Follow-up (follow_up_text, Instagram and Facebook): one more DM follow_up_delay_hours (1 to 23, default 23) after the answer, with an optional link button (follow_up_button_title + follow_up_button_url). On an Instagram comment with Follow first off, the first DM becomes a tap step with one button (follow_up_tap_text, follow_up_tap_button; defaults "Tap the button and I'll send you the link 👇" and "Send me the link"): the tap sends dm_text and opens Meta's window, and people who never tap get neither the link nor the follow-up, so tell the user. A DM or story reply trigger needs no tap step; on Facebook only people who answer the DM get the follow-up. It is skipped when the person said stop, a team member answered them by hand, or their last tap or message is older than about 24 hours. X has none (400 follow_up_not_supported). Show the user the follow-up text and the delay before creating it. To attach automations to a NEW post, pass comment_dm_automation on create_post instead (Instagram and Facebook).
Inputs: name, match, scope, status, +22 more.
create_folderAInspect
Create a media-library folder. Use it to organize assets (e.g. a 'win-graphics' folder), then upload into it with upload_media (folder) or move files with update_media (folder_id).
Inputs: name (required), parent_id.
create_hashtag_setAInspect
Save a reusable, named group of hashtags (e.g. 'Fitness Brand' -> #fitness #gym #workout). Tags may include or omit the leading '#'; they are deduped case-insensitively and kept in order (max 100). Then apply the set to any new post via create_post (hashtag_set).
Inputs: name (required), hashtags (required).
create_postAInspect
Create a new social media post, story, or reel.
IMPORTANT — Before calling this tool, make sure you have all required information from the user. If anything is missing, ASK the user before calling:
Workspace: If the user has only one workspace, just use it (no need to ask). If the user has named a workspace in their request, switch to it once and remember it for the rest of the conversation. If multiple workspaces exist and the user has NOT named one, call
list_workspacesand ASK which workspace to post to before continuing. Never silently pick a workspace when more than one exists — each workspace has different connected channels and different audiences. After a successful create/schedule/publish, mention the workspace name in your reply for clarity (e.g. "Scheduled to the Acme workspace for Tuesday 3pm").Content/caption: What text should the post have? If captions differ per platform, use one call with an object: { "default": "fallback text", "linkedin": "long version", "threads": "short version", "x": "short version", "bluesky": "short version" }. Always prefer one call per topic. RESPECT character limits per platform (see below).
Channels: Which platforms to post to? Call
list_accountsto show available options for the active workspace. Ask the user which channels to use.Schedule: When should it be published? (Or save as draft?)
Media (REQUIRED for some types):
Stories: ALWAYS require an image or video. A story can carry up to 10 media items: each item is one slide, published as its own story in the order given. Ask the user which slides and in what order.
Reels: ALWAYS require a video.
Instagram posts: ALWAYS require at least one image or video.
TikTok posts: ALWAYS require at least one image or video.
Pinterest posts: ALWAYS require an image AND a board_id.
Other platforms (LinkedIn Profile, LinkedIn Page, X, Bluesky, etc.): Media is optional.
Image fit (aspect ratio): a feed image outside what a channel shows uncropped is handled PER CHANNEL. Instagram shows feed images between 4:5 and 1.91:1: a 9:16 (story-style) image posted to the Instagram feed is CROPPED to 4:5 around the subject by default, because Instagram cuts it to that window anyway and Meta cannot boost a feed post outside it. Pinterest keeps a Pin taller than 2:3 and reports it. Before posting a tall image to Instagram, run
check_media_compatibility(its fit rows say per connected channel whether the image fits and what the default does) and ASK the user: crop to 4:5 (recommended: Meta can boost it) or keep the original (Instagram cuts it itself, no boost)? Pass the answer asmedia_fit: { instagram: "crop" | "keep" }. If the user gave no preference, let the default run and RELAY theimage_fitwarning from the response (it names the crop and how to undo it with update_post). Stories, reels and videos are never cropped; 'default' and the other channels keep the original. Never drop a channel over this.
Platform-specific options (ask only when relevant):
Pinterest board (auto-default to first board): If Pinterest is in
channelsandpinterest.board_idis NOT provided, do NOT block on asking the user — and do NOT skip Pinterest. Instead:Call
get_accounton the Pinterest account — the response includes aPinterest Boardstable with each board's name and ID.Use the FIRST board in that list as
pinterest.board_idautomatically.In your reply, explicitly mention which board you used (e.g. "Posted to your 'Marketing' board on Pinterest — let me know if you'd prefer a different one and I'll move it.") so the user can correct course. If the user named a board ("post to my Marketing board") or specified one in the request, match it (case-insensitive) against the list and use that one instead of the first.
YouTube: Title, privacy status, tags?
TikTok: Privacy level?
X threads vs long-form: A chained "thread" (the user explicitly asks for one) → pass
x.thread_partsas an array of 2–25{ text }objects (each ≤ 280 chars); the top-levelcontentis then ignored for X. A single long-form post on a Basic, Premium or Premium+ account → just put the full text (up to 25,000 chars) incontent— no threading needed (checkplatform_details.subscription_typevia list_accounts). On a free account, X caps a single post at 280 chars, so either split into a thread or shorten. Never cram "1/", "2/" prefixes intocontent— that posts one tweet, not a thread.X posts containing a link: X treats a post whose text contains a link written with http:// or https:// as a link post (a bare domain such as brand.com or a www. link does not count; in a thread, every part with such a link). Link posts on X are a feature the organisation enables on its OmniSocials account. When it is not enabled, the request is refused with an
x_feature_not_enablederror that says so: tell the user, offer to post without the link or without X, and do not retry as is. Never remove a user's link without asking them.
VIDEO DURATION CAPS — MUST RESPECT THESE (returns 400 validation_error when exceeded):
Platform | Post mode | Reel mode |
240 min | 240 min (the old 90 s Reel cap is gone) | |
YouTube Short | (no Post mode) | 3 min |
X | 140 s | N/A |
Bluesky | 10 min | N/A |
Threads | 5 min | N/A |
TikTok | 10 min | 10 min |
LinkedIn / LinkedIn Page | 30 min | N/A |
15 min | 15 min | |
15 min | N/A | |
15 min | N/A | |
Mastodon | (instance-dependent) | N/A |
Telegram | (no cap, 50 MB file limit) | (no cap, 50 MB file limit) |
Discord | (no cap) | (no cap) |
VIDEO FILE-SIZE CAPS — MUST RESPECT THESE (validated via ffprobe at schedule/publish time; drafts exempt):
Platform | Video cap |
Telegram | 50 MB |
Mastodon | 99 MB |
Discord | 1 GB (a file over 20 MB goes as a link in the message) |
Bluesky | 300 MB |
300 MB | |
X (free tier) | 512 MB |
Threads / Reddit | 1 GB |
2 GB | |
Facebook / TikTok | 4 GB |
LinkedIn / LinkedIn Page | 5 GB |
YouTube | 256 GB |
Upload requests are capped at 100 MB on top of these; anything bigger gets rejected with code: file_too_large before the validator runs.
Cap-violation error shape (one sentence per offending platform):
{ "error": { "code": "validation_error", "message": "YouTube only allows videos up to 3min; yours is 3min 12s. Trim the video or deselect YouTube." } }Before sending an oversized video, warn the user and offer to trim, deselect that platform, or split. Drafts can still be created without media — the validator only runs when transitioning to scheduled or publish_now.
CHARACTER LIMITS — MUST RESPECT THESE:
Platform | Max chars | Notes |
X (free / Basic) | 280 | Long posts require Premium or Premium+ — Basic does NOT count |
X (Premium / Premium+) | 25,000 | Check platform_details.subscription_type on the account |
Bluesky | 300 | Counted in graphemes |
Mastodon | 500 | Default (mastodon.social); the connected server's own limit applies, links count as 23 |
Threads | 500 | |
YouTube | 500 | Description field |
800 | Pin description | |
2,200 | Caption | |
TikTok | 2,200 (videos) / 4,000 (photo posts) | Videos have a single caption field |
3,000 | ||
63,206 | Very generous | |
Telegram | 4,096 | With media, text over 1,024 goes as a reply under the media; a poll question is max 300 |
Discord | 2,000 | A poll question is max 300 |
When posting to multiple platforms with different limits, ALWAYS use per-platform captions. For example, if posting to LinkedIn (3000 chars) and X (280 chars), use: { "default": "full version", "x": "shortened version" }. Never post content that exceeds a platform's limit.
Channel IDs you can pass: instagram, facebook, threads, linkedin (personal profile), linkedin_page (company page), youtube, tiktok, pinterest, x, bluesky, mastodon, telegram (a Telegram channel or group), discord (a Discord channel). linkedin and linkedin_page are independent. A workspace can have both connected and post to each separately. Always confirm with list_accounts which are actually connected.
Do NOT call this tool without media when creating stories, reels, Instagram posts, TikTok posts, or Pinterest posts — it will fail.
IMPORTANT - When the user shares an image or screenshot in chat: You MUST upload it before creating the post. Do NOT skip the image. Do NOT create a text-only draft when an image was provided. Follow these steps:
Call
upload_mediawithmethod="upload_url"to get upload instructionsUse code execution to upload the image file to OmniSocials
Use the returned media ID in
media_idswhen creating the post Only if code execution is completely unavailable, save as a draft and tell the user to add the image at app.omnisocials.com.
Inputs: content (required), x, tags, type, +32 more.
create_tagAInspect
Create a post tag, e.g. 'Question hook', 'Talking head' or 'Spring campaign'. A name is unique in the workspace (case-insensitive). At most 200 tags per workspace. Tags can also be made on the fly: a new name in tags on create_post / update_post or in tag_posts becomes a tag.
Inputs: name (required), color.
create_webhookBInspect
Create a new webhook. Available events: post.scheduled, post.published, post.failed, post.approved (the last approval of a post's approval workflow is in), post.rejected (an approver rejected the post)
Inputs: url (required), events (required).
delete_automationADestructiveInspect
Delete a comment-to-DM automation (Instagram, Facebook Page or X) and its activity log. DMs that were already sent stay sent. To stop it for a while, use update_automation with status 'paused' instead. Confirm with the user first.
Inputs: automation_id (required).
delete_hashtag_setADestructiveInspect
Delete a saved hashtag set. Posts that already used it keep their hashtags — the tags were merged into their captions at create time.
Inputs: set_id (required).
delete_inbox_commentADestructiveInspect
Permanently delete a comment on one of the workspace's posts, on the platform and from the inbox: a comment someone left, or a reply the workspace's own account posted (for example one sent under the wrong comment). Facebook, Instagram and TikTok comments only. On TikTok only replies the workspace's own account posted: TikTok and YouTube do not let an account delete comments other people left, so use hide_inbox_comment for those. Replies under the comment are deleted with it. When the account's last reply under a comment is deleted, that comment counts as unanswered again and get_next_unanswered serves it. This cannot be undone: confirm with the user before calling. Takes the message id (the #id in the thread), not the conversation id. A 403 reconnect_required means the account must be reconnected in the dashboard to grant the moderation permission.
Inputs: message_id (required).
delete_mediaBDestructiveInspect
Delete a media file by ID.
Inputs: id (required).
delete_postADestructiveInspect
Delete a post by ID. This action cannot be undone.
Inputs: id (required).
delete_tagADestructiveInspect
Delete a post tag. It comes off every post of the workspace; the posts stay. Cannot be undone: confirm with the user first.
Inputs: id (required).
delete_webhookCDestructiveInspect
Delete a webhook by ID.
Inputs: id (required).
get_accountARead-onlyInspect
Get details of a specific connected social media account. An X account also shows its X statistics setting (how often its posts are checked and its followers counted); change it with set_x_statistics.
Inputs: id (required).
get_account_analyticsARead-onlyInspect
Get account-level analytics for all connected platforms: followers, following, posts, and the day values the platform reports for the snapshot date (impressions/views, reach, engagement, profile_views, link_clicks, follows_gained, follows_lost, Google Business calls/direction_requests/website_clicks/average_rating/review_count, Pinterest monthly_views). Rows with day values carry period: "daily". Audience objects appear when available: demographics (+ demographics_unit) and online_followers (UTC hour to followers online). Present as a sorted table by follower count. Metric semantics: LinkedIn profile rows keep a lifetime total under impressions_lifetime (all content ever, including posts published outside OmniSocials) and period: "lifetime" when no daily breakdown is served. A missing key means the platform does not report it. Each metrics object carries a note explaining its scope where semantics are non-obvious; always relay that note to the user.
Inputs: date, platform.
get_analytics_overviewARead-onlyInspect
Get analytics overview with total posts, impressions, engagements, engagement rate, and per-platform breakdown. Use period for a rolling window (7d / 30d / 90d) or start_date + end_date for a custom range. The response echoes the resolved range and today's date — read those before assuming a year from training data (e.g. when the user says 'April', use the most recent April, not April from your training cutoff).
Inputs: tag, period, end_date, start_date.
get_automationARead-onlyInspect
Get one comment-to-DM automation: its platform (Instagram, the Facebook Page or X), its trigger, the DM text, the public replies, Follow first (Instagram), the follow-up (Instagram and Facebook), the limits and the counts (with the follow-ups sent and skipped).
Inputs: automation_id (required).
get_automation_activityARead-onlyInspect
The activity of a comment-to-DM automation, newest first: one row per comment or message it acted on, with the DM sent, an answer that waits in the queue (queued: the send cap is full or the platform asked to wait; it goes out as soon as there is room), a skip and its reason (already got the DM, limit reached, comment older than 7 days, the send cap stayed full for a day on Instagram and Facebook or an hour on X, the person does not accept DMs from the X account, the person replied STOP earlier, the automation was paused while the answer waited), a person who replied STOP on X (opted_out: no automatic DMs to them from that X account again, in any workspace or automation), or a failure with the platform's error. With Follow first (Instagram) a row can be waiting (asked to follow, no link yet: it shows whether the person tapped the button and how often), a skip can say the person was already asked to follow, and a sent row says whether the person followed after the ask, already followed, or got the link without a check. With a follow-up (Instagram and Facebook) a row can be waiting for the tap (the tap step on an Instagram comment: no link until the person taps), and each sent row says where its follow-up is: due at a time, sent, or kept back with the reason (no tap or message from the person in Meta's 24-hour window, the person said stop, a team member answered by hand, the automation or the follow-up was switched off). On the Facebook Page the person shows by name (Facebook has no @handle). Use it to answer 'how many people got the DM' or 'why did this person not get it'.
Inputs: automation_id (required), limit, offset, outcome.
get_best_timesARead-onlyInspect
Get recommended posting times (day + hour) for one platform, computed from the workspace's own posting history: publish time × engagement of every post published there, recency-weighted and outlier-damped, bucketed in the user's timezone, and blended with when the account's followers are online when the platform provides that (Instagram, TikTok Business; basis: own_data_and_audience, response carries audience_online). Returns the top 3 recommended slots plus a per-day breakdown. When the workspace has fewer than 15 analyzed posts on the platform, the audience-online profile alone is used (basis: audience) or industry-average defaults are returned (basis: defaults) with how many more posts unlock personalized recommendations — tell the user that so the numbers aren't mistaken for their own audience data. Use this before scheduling when the user asks 'when should I post?' or hasn't specified a time. Requires the analytics:read scope.
Inputs: platform (required), timezone.
get_calendarARead-onlyInspect
Get a content calendar showing scheduled and published posts organized by day of the week.
Inputs: status, end_date, start_date.
get_inbox_conversationARead-onlyInspect
Get the full message history of one inbox conversation, oldest first, with the post it belongs to (caption, link, image) for comment/mention threads. Each message shows its inbox id (#id); that id is what like_inbox_comment, hide_inbox_comment and delete_inbox_comment take. Use the conversation_id from list_inbox_conversations. Replies sent from the native apps appear as outgoing messages too.
Inputs: conversation_id (required), limit, cursor.
get_limitsARead-onlyInspect
What OmniSocials cannot do, why, and what to do instead: platform rules (for example, TikTok's API cannot delete a video), features OmniSocials has not built yet, and features that work only in the OmniSocials app. Call it before you tell the user that OmniSocials cannot do something, and when no other tool fits what the user asked, so you can give the real reason. Filter by platform or area. An entry the user still wants can be asked for with request_feature (its id as limit_id), unless it is a platform rule.
Inputs: area, platform.
get_next_unansweredARead-onlyInspect
Get the next inbox item that needs an answer, with the whole conversation and the post it is on, in one call. An item needs an answer when it is the customer's latest DM with no reply after it, or a comment/mention nobody replied to and that is not hidden. Order: DMs that can still be answered first (Instagram/Facebook DMs inside Meta's 24-hour window, the one closing soonest first, plus X DMs), then Instagram/Facebook DMs whose window has closed (reply_window.open = false: OmniSocials cannot reply, tell the user to answer from the native app or skip with mark_inbox_read), then comments and mentions, oldest first. Replies typed in the native apps count as answered (they are mirrored into the inbox), so a thread a colleague answered on their phone is not served again. Instagram mentions are skipped (no reply path). Only unread items are served by default: to skip one for good, mark_inbox_read it; pass include_read to also see read-but-unanswered items. Looks back 30 days. Loop: get_next_unanswered → draft a reply → reply_to_inbox with the conversation id, message_id = the served message's #id, and include_next: true → repeat until nothing is waiting.
Inputs: type, order, exclude, platform, +1 more.
get_postARead-onlyInspect
Get full details of a specific post including content, channels, media (with URLs), first comment, Instagram collaborators/user tags/location/Trial Reel state/Reel cover (thumbnail_type + thumb_offset in ms), dates, live URLs, per-platform publish errors, and retry linkage (retry_of / retries — a published post with empty published_urls and retries set is a resolved failure whose live URLs live on the retry post) — enough to fully verify a scheduled post without opening the dashboard. When a post has per-platform caption overrides (e.g. a shorter X version alongside the default), every variant is rendered as its own labeled block under ### Content so you can see exactly what each platform will publish. X threads are rendered under ### X Thread with each tweet labeled in publish order — read this to see the full chained tweet text, since thread-only posts have no caption in content. A LinkedIn poll is rendered under ### LinkedIn Profile Poll and/or ### LinkedIn Page Poll (independent per channel) with the question, options, and duration. After a post is published, published_urls maps each platform to the live post URL (only platforms that successfully posted appear).
Inputs: id (required).
get_post_analyticsARead-onlyInspect
Get detailed analytics for a specific published post. Renders every metric the platform reported — impressions, reach, views, saves, likes, comments, shares, clicks, engagements, and more — per platform. TikTok videos also carry average_time_watched, full_video_watched_rate, total_time_watched, favorites and reach when the workspace enabled TikTok comments (Business API authorization).
Inputs: post_id (required).
get_post_approvalARead-onlyInspect
Read the approval review of a post: every workflow step with its approvers and their decisions, the rejection with its reason, and the comment thread. Use it when get_post shows status rejected (who rejected it and why, what to change before sending it again) or in_approval (who the post waits for, what the reviewers wrote). Read-only. A post without an approval workflow returns status none.
Inputs: id (required).
get_posts_analyticsARead-onlyInspect
Get analytics for several published posts at once (up to 100), each totalled into impressions and engagements. Use this instead of calling get_post_analytics in a loop — it is a single request rather than one per post.
Inputs: post_ids (required).
get_post_statusPost Card StatusARead-onlyInspect
Used by the OmniSocials post card to follow a post while it publishes. Agents: use get_post instead.
Inputs: id (required).
get_recent_platform_postsARead-onlyInspect
Fetch the user's most recent posts straight from their connected platform APIs (Instagram, TikTok, X, YouTube, Facebook, LinkedIn, and more), INCLUDING content published outside OmniSocials. Use this when list_posts is empty — e.g. a brand-new workspace that has not published through OmniSocials yet — so you can still analyze the user's real content. Each post includes normalized engagement plus every raw metric the platform reported (Instagram: reach/views/saves/shares from per-post insights; TikTok: average_time_watched/full_video_watched_rate/total_time_watched/favorites/reach when the workspace enabled TikTok comments). Metrics only appear where the platform exposes them for historical posts (X, TikTok, Bluesky, Mastodon, Instagram, Facebook, YouTube); Threads, Pinterest, and Google Business return captions only. Records also carry duration_seconds — the video length in whole seconds — where the platform's listing API reports it (currently TikTok and YouTube); null for images and platforms that don't expose it. LinkedIn personal profiles can't be listed live (LinkedIn grants apps no such permission), so their results are posts published through OmniSocials with their latest collected stats. Fetched live for most platforms, so expect a few seconds of latency; X results may come from a snapshot up to 24h old (X bills per returned post) — the snapshot refreshes right after the user publishes to X through OmniSocials. Output is a human-readable summary table PLUS a 'Structured data' JSON block carrying, for every post, the platform's own post id (the stable dedupe key), a permalink, the FULL untruncated caption, and exact-integer metrics — use that block when ingesting or storing native posts rather than the rounded/truncated table. Requires the analytics:read scope.
Inputs: limit, platforms.
get_tag_analyticsARead-onlyInspect
Compare post tags: for each tag, how its published posts did against the user's normal in a period (the Tags tab of Analytics). vs normal is fair across channels: each post is measured against the median impressions of its own channel, so a tag does not win just because its posts went to the channel with the most views. A tag with fewer than min_posts measured posts is marked 'too few posts': say so instead of drawing a conclusion. Default period: the last 90 days.
Inputs: end_date, platform, min_posts, start_date.
get_webhookBRead-onlyInspect
Get details of a specific webhook by ID.
Inputs: id (required).
hide_inbox_commentAInspect
Hide (or unhide) a comment someone left on one of the workspace's posts, on the platform, as the post owner. Facebook, Instagram, TikTok, YouTube and Threads comments. On YouTube, hide sets the comment to 'rejected' (removed from public view together with its replies) and unhide publishes it again. Takes the message id (the #id shown by get_inbox_conversation and get_next_unanswered), not the conversation id. A hidden comment no longer counts as unanswered. If the comment was already deleted on the platform (its author removed it, etc.), this still succeeds — the response says so — and the item is marked handled; do not retry it. A 403 reconnect_required means the account was connected without the comment-moderation permission and must be reconnected in the dashboard; relay that to the user rather than retrying. A 422 cannot_hide means Facebook does not let the Page hide this particular comment (the commenter blocked the Page, their account is deactivated or restricted, or the comment sits on a shared copy of the post): retrying never changes it — tell the user, and use mark_inbox_read on the conversation if it should stop coming up. A 502 hide_not_applied means Instagram accepted the call but still reports the comment as visible (this happens with comments shown under 'Comments from Facebook' on a reel shared to Facebook; they live on Facebook and Instagram's hide does not reach them): nothing changed in the inbox, tell the user to hide it in the Instagram or Facebook app, do not retry.
Inputs: message_id (required), hide.
like_inbox_commentAIdempotentInspect
Like (or remove the like from) a comment someone left on one of the workspace's posts, as the connected account: the Facebook Page, the LinkedIn Page or the TikTok account. Incoming Facebook, LinkedIn Page and TikTok comments only. Facebook allows a Like only: no app can add Love or another reaction, so say so when the user asks for one. Takes the message id (the #id shown by get_inbox_conversation and get_next_unanswered), not the conversation id. Liking an already liked comment succeeds and changes nothing. A like does not mark the comment as read or answered: to move past it in get_next_unanswered without a reply, use mark_inbox_read or exclude. Like only comments the user asked you to like, or that match a rule the user gave (for example 'like the positive comments'); never like in bulk on your own. A 403 reconnect_required or 401 reauth_required means the account must be reconnected in the dashboard; relay that to the user rather than retrying.
Inputs: message_id (required), like.
list_accountsARead-onlyInspect
List all connected social media accounts for the active workspace. If the user has multiple workspaces, call list_workspaces first so they can pick which one to work with. X accounts also show their X statistics setting: how often their posts are checked (full = 5 checks, light = 2 checks, off) and their followers counted (daily, weekly, off); change it with set_x_statistics.
Inputs: no named parameters.
list_approval_workflowsARead-onlyInspect
List the approval workflows this workspace can use (company-wide ones plus workspace-bound ones), with their steps and named approvers. Workflows are created in the OmniSocials dashboard (Approvals); this tool only lists them. Pass a workflow's id as approval_workflow_id on create_post to hold a scheduled post for review: it is created as in_approval, the approvers are notified, and it publishes at schedule_at once the last step approves. Call this first when the user wants agent-created posts to be reviewed/approved before publishing; if the list is empty, tell the user to create a workflow under Approvals in the dashboard.
Inputs: no named parameters.
list_automationsARead-onlyInspect
List the comment-to-DM automations of this workspace, on Instagram, on the Facebook Page and on X. An automation DMs a person once when they comment a keyword on a post (or send it in a DM, or in an Instagram story reply), with an optional public reply under the comment; on X it answers DMs only. Use it to answer 'which automations run', before creating one on a post that may have one already, or to find the id for update_automation / get_automation_activity.
Inputs: status, post_id, platform.
list_feature_requestsARead-onlyInspect
The feature requests the signed-in user sent (from the OmniSocials app, an AI assistant, the API or the CLI), newest first, with their status and the OmniSocials team's replies. Use it when the user asks what happened to a request.
Inputs: no named parameters.
list_foldersARead-onlyInspect
List the media-library folders in this workspace (Finder-style organization). Returns each folder's id, name, parent, and item count. Use a folder id with list_media (folder_id) or update_media (folder_id), or a folder name with upload_media (folder).
Inputs: no named parameters.
list_hashtag_setsARead-onlyInspect
List the saved hashtag sets in this workspace. Apply one to a new post by passing its name via create_post (hashtag_set) — the tags are appended to the captions or, with hashtag_placement='first_comment', posted as the auto first comment.
Inputs: no named parameters.
list_inbox_conversationsARead-onlyInspect
List social inbox conversations (Instagram/Facebook DMs, comments, mentions, LinkedIn company-page comments/mentions, TikTok video comments, YouTube video comments, X DMs where the workspace has opted into X DMs, and Threads replies on the workspace's posts plus mentions), newest activity first. Cursor-paginated: pass the returned cursor to get the next page. To work through what needs answering one item at a time, use get_next_unanswered instead.
Inputs: type, limit, cursor, unread, +2 more.
list_mediaARead-onlyInspect
List media files in the workspace. Shows each file's name, folder, type (image, video, or document: a PDF kept as one item whose ID in media_ids expands into every page), size, a preview link, and its media ID for use when creating posts. To reuse an existing graphic, SEARCH for it by name here FIRST instead of re-uploading — re-uploading the same image creates duplicates. Organize assets into folders with create_folder / list_folders.
Inputs: limit, offset, search, folder_id.
list_pinterest_productsARead-onlyInspect
List the product Pins of the connected Pinterest account, to tag products on a Pin (Pinterest shows the tagged items on the image). Use this whenever the user wants to tag products on a Pinterest post.
Flow: call it → show the products to the user → pass the chosen pin_id values (max 24) as pinterest.product_tags on create_post / create_and_publish_post / update_post. If the user gives a Pin link or Pin ID of a product, pass it as check_pin to check it first, or put it straight in pinterest.product_tags.
Notes:
Only the account's own product Pins can be tagged: a public product Pin with a link on a website the account claimed on Pinterest. Products of other merchants cannot be tagged through the API.
source"catalog" reads the Pinterest catalog. It needs catalog access, which the user gives one time in OmniSocials: create a post, open the Pinterest options, select Add products, then Connect catalog.source"pins" reads the account's own Pins and returns the product Pins; one call scans up to 250 Pins, so an empty result with a bookmark means: call again with that bookmark. Withoutsource, the catalog is used when the connection has catalog access, else the Pins.A product that Pinterest refuses never fails the post; get_post shows which products were tagged.
Inputs: source, bookmark, check_pin, product_group_id.
list_postsARead-onlyInspect
List posts in the workspace. Filter by status to see drafts, scheduled, published, or failed posts. Returns a formatted table with content preview, channels, dates, and post IDs. The content cell shows the default caption; if a post has per-platform overrides (e.g. a custom X version) the preview is suffixed with (per-platform) — call get_post to see every variant.
Inputs: tag, limit, offset, status.
list_tagsARead-onlyInspect
List the workspace's post tags (the team's own labels for its posts: a hook style, a format, a campaign). Tags filter list_posts (tag) and get_analytics_overview (tag), and get_tag_analytics compares them. Reuse these exact names when tagging so no near-duplicates appear.
Inputs: no named parameters.
list_webhooksARead-onlyInspect
List all configured webhooks with their status, events, and last trigger time: the webhooks of the active workspace and the organisation-wide webhooks made in the OmniSocials dashboard (scope 'Organisation': they receive the events of every workspace). A webhook switches off by itself when the person who set it up no longer has access to the organisation or workspace (status Inactive, the reason under Last failure in get_webhook); update_webhook with is_active true switches it on again.
Inputs: no named parameters.
list_workspacesARead-onlyInspect
List all workspaces the user has access to. Workspace selection rule: if only one workspace is available, just use it (no need to ask). If the user has named a workspace in their request (e.g. 'post to my Acme workspace'), proceed with that workspace and remember it for the rest of the conversation. If multiple workspaces exist and the user has NOT named one, call this tool, present the list, and ASK the user which one to use before posting, switching, or fetching analytics. After a successful action, mention the workspace name in your reply for clarity.
Inputs: no named parameters.
mark_inbox_readBInspect
Mark all incoming messages in a conversation as read.
Inputs: conversation_id (required).
publish_postADestructiveInspect
Publish a draft or scheduled post immediately. Only draft and scheduled posts can be published — for a failed or partially failed (warning) post use retry_post instead, which re-publishes only the failed platforms.
Inputs: id (required).
reject_postAInspect
Reject a post's approval workflow. Only works on a post with approval_status 'pending' (post status in_approval) — check get_post first. IMPORTANT: only succeeds if the connected user is a listed approver for the workflow's CURRENT step (same requirement as approve_post). Unlike approval, a rejection stops the WHOLE workflow immediately, not just the current step — the post's status becomes rejected and it will not publish. Pass comment to explain why; it's shown to the requester and other approvers in the post's review thread. Pass step_order (the current_step from get_post_approval) as with approve_post; on step_changed, read the review again before you decide.
Inputs: id (required), comment, step_order.
reply_to_inboxADestructiveInspect
Reply to an existing inbox conversation (DM, comment, or mention) on Instagram, Facebook, LinkedIn, TikTok, YouTube, X, or Threads. You can only reply to conversations that already exist. For a comment or mention, pass message_id (the #id of the comment being answered): comments on one post share a conversation and without it the reply goes under the newest comment on the post. Meta direct-message replies must be within the platform's 24-hour messaging window: a 422 outside_messaging_window means the window has closed, nothing was sent, and the user must answer that DM from the Instagram or Facebook app (mirrored into the inbox) or skip it with mark_inbox_read; do not retry. TikTok replies are comments only, text-only, and capped at 150 characters; they can take a few minutes to appear on TikTok while they pass spam review. YouTube replies are comments only. Threads replies are on the workspace's posts and mentions; a 401 reauth_required means the Threads connection must be reconnected to grant the reply permission. X replies are DM-only; an x_feature_not_enabled error means X direct messages are not enabled on this organisation's OmniSocials account at the moment: nothing was sent, tell the user and do not retry. attachment_url/attachment_type let you send media on a Facebook or Instagram DM (text is optional when an attachment is set); other platforms are text-only. Set include_next: true to get the next conversation that needs an answer back in the same call (same as get_next_unanswered), so the inbox can be worked through as: get_next_unanswered → draft → reply_to_inbox(include_next) → draft → repeat. A 409 duplicate_reply means this exact reply already went out to this conversation in the last 10 minutes (an earlier call that looked slow or failed did succeed) or is being sent right now: nothing was sent again, do NOT retry it — continue with get_next_unanswered. A 422 reply_not_allowed means the platform refuses replies to this item for good (Facebook #1705: the comment sits on a share or boosted copy of the post, or the commenter restricts replies; YouTube: the thread's canReply is false because comments are off on the video or the comment was removed or held for review): the item is dropped from get_next_unanswered automatically, tell the user, and do NOT retry.
Inputs: conversation_id (required), text, message_id, include_next, +2 more.
request_featureAInspect
Send a feature request to the OmniSocials team for the signed-in user. Call it only after the user said yes to sending it. Write summary yourself: what the user wants to do and why, in one or two sentences. Never put the conversation, other people's personal data or secrets in it. The request is stored with the user's name and email so the team can answer. The user sees it in OmniSocials (Settings, Request a feature) and gets an email when its status changes. Pass limit_id when the request matches an entry of get_limits; a platform rule cannot be requested. At most 10 requests an hour.
Inputs: summary (required), area, title, limit_id, +1 more.
retry_postADestructiveInspect
Retry the failed platforms of a failed or partially failed post — on the same post, no duplicate created. Use when a post has status failed (every platform failed) or warning (some failed, some published): only the FAILED platforms are re-published; platforms that already succeeded are never posted again. Runs asynchronously (usually within a few minutes) — poll get_post afterwards: on success the status becomes published and published_urls gains the platform's live URL. Max 3 retries per platform; after that, recreate the post. Note publish_post refuses failed posts; this is the tool for them.
Inputs: id (required).
rotate_webhook_secretADestructiveInspect
Rotate the signing secret for a webhook. The new secret will only be shown once. The old secret keeps signing for 24 hours: every delivery then carries X-OmniSocials-Signature (new secret) and X-OmniSocials-Signature-Previous (old secret, same format), so the receiving endpoint keeps accepting deliveries while it switches to the new secret.
Inputs: id (required).
search_instagram_audioARead-onlyInspect
Search Instagram's licensed music catalog for a track to attach to a REEL. Use this whenever the user wants to post a reel WITH music/a song/a sound (e.g. "post this reel with trending audio", "add that song to it").
Flow: call with a song/artist/keyword (or NO query for currently trending audio) → present the options → once the user picks, pass that result's audio_id as instagram.audio_id on create_post / create_and_publish_post / update_post. Optionally mix with instagram.audio_volume / instagram.video_volume (0-100; set video_volume 0 to fully replace the video's own sound). Instagram Reels only — feed posts, carousels, and Stories can't take music via the API (Meta limitation).
Notes: only tracks Meta licenses for third-party publishing appear, so the selection can differ from the Instagram app. Requires the workspace to have a Facebook account connected whose Page is linked to this Instagram account — if results say Facebook is needed, tell the user to connect it under Settings → Organisation → Workspaces.
Inputs: type, query.
search_locationsARead-onlyInspect
Search for a location to tag on a post. Use this whenever the user wants to post WITH a place/location (e.g. "tag my dealership", "post this at the café"). It returns matching real venues with their addresses and a location ID.
Pick the platform with platform: "instagram" (default) or "threads". The two use DIFFERENT ids (a Facebook Place ID is not a Threads location id), so search with the platform you will tag. If the user wants both, search twice.
Flow (Instagram): call with the place name → present the options → once the user picks, pass that result's id as the top-level location_id on create_post / create_and_publish_post / update_post.
Flow (Threads): same, but pass the id as threads.location_id. On a multi-post thread the tag goes on the first post.
Notes: use a SPECIFIC venue name (a broad brand like "Starbucks" returns individual store locations). Instagram: if the user already has a numeric Facebook Place ID, you can pass it straight to create_post; it's validated at publish and a bad one returns a clear error. If results are empty with a permission note, the workspace's Facebook app can't search arbitrary places — tell the user to use their own business Page's ID. Threads: needs the workspace's Threads connection to have the location permission; if the result says to reconnect Threads, tell the user to reconnect it under Settings → Organisation → Workspaces.
Inputs: query (required), platform.
set_x_statisticsADestructiveIdempotentInspect
Choose how often the posts of an X account are checked (full = 5 checks: about 5 hours after publishing, day 1, 3 and 7, and day 30 for posts with 100+ views; light = 2 checks: about 5 hours and day 7; off) and how often its followers are counted (daily, weekly, off). Send posts, followers or both; a value left out stays as it is. Tell the user what the choice means and ask before calling. X accounts only (the account id ends in _x). Changing it needs the organisation owner or an admin of the organisation (an API key also needs the opt-in accounts:write scope, set when the key is made). list_accounts and get_account show the current setting.
Inputs: account_id (required), posts, followers.
switch_workspaceAInspect
Switch the active workspace by NAME. All subsequent tool calls (posts, media, analytics, etc.) will operate on the selected workspace. Pass the workspace name exactly as shown in list_workspaces (its id or list position also work, but the name is preferred and unambiguous). Only call this when the user has explicitly named the target workspace, or after the user has picked one from list_workspaces. Never call switch_workspace silently when the user hasn't specified a workspace - ask first.
Inputs: workspace (required).
tag_postsAInspect
Add, remove or replace the tags of up to 500 posts at once, published posts included (tags never go to a platform). Use it to tag older posts so get_tag_analytics has enough posts to compare: find them with list_posts, read their captions, then tag them. add / set take tag names or ids (a new name becomes a tag); remove takes names or ids; set replaces a post's tags.
Inputs: post_ids (required), add, set, remove.
update_automationADestructiveInspect
Change a comment-to-DM automation: pause or resume it (status), new keywords or match, a new DM text or public replies, new limits, or move it to another post (post_id, instagram_media_id or facebook_post_id). Only the fields you pass change. follow_gate true or false switches Follow first (Instagram) on or off and keeps its texts; new Follow first texts keep the switch as it is. follow_up false switches the follow-up off and keeps its texts; a new follow_up_text switches it on; follow_up_delay_hours, the button and the tap step texts alone change only themselves (null for the button removes it). The platform cannot change: to move to another channel (Instagram, the Facebook Page or X), create a new automation. Turning an X automation on (status 'active') needs X DMs on for the workspace, else 409 x_dms_off. A 'completed' automation starts again when its limits or trigger change.
Inputs: automation_id (required), name, match, scope, +23 more.
update_hashtag_setAInspect
Rename a hashtag set and/or replace its tags. 'hashtags' replaces the FULL list — to add or remove tags, pass the complete new list (see list_hashtag_sets for the current tags). Posts that already used the set are unaffected.
Inputs: set_id (required), name, hashtags.
update_mediaAInspect
Rename an existing media file or move it into a folder (so it's findable later instead of re-uploading it). Only the fields you pass are changed.
Inputs: id (required), name, folder_id.
update_postADestructiveInspect
Update an existing post. Only draft and scheduled posts can be updated.
Per-platform options (youtube, pinterest, instagram, tiktok, google_business) are accepted here, same shape as in create_post. Pass an object — never a JSON-encoded string. For YouTube Shorts, the title lives at youtube.title; the video description lives in content (or content.youtube for a per-platform override). They are not the same field — changing the caption does NOT rename the Short.
X threads: To convert an existing draft into a chained X thread, pass x.thread_parts as a 2–25 entry array of { text } objects (each ≤ 280 chars). Pass x.thread_parts: null to revert to single-tweet mode. Do NOT shove "1/", "2/" into content — that's a single tweet, not a thread.
Inputs: id (required), x, tags, tiktok, +28 more.
update_post_analyticsAInspect
Check the X numbers of a published post again now. Works on posts published to X (refresh_not_available otherwise). The regular checks run on their own schedule (set_x_statistics); call this only when the user asks for fresh numbers of a post. At most 5 checks of a post a day (the regular checks count too) and 100 for the whole organisation (refresh_limit). x_feature_not_enabled when checking X statistics now is not enabled on the organisation's OmniSocials account (an organisation owner can enable it in OmniSocials; the numbers already stored stay); refresh_failed when X did not answer. Returns the new numbers per tweet.
Inputs: post_id (required).
update_tagBInspect
Rename or recolour a post tag. Posts keep the tag.
Inputs: id (required), name, color.
update_webhookADestructiveInspect
Update a webhook's URL, events, or active status. Works on workspace and organisation-wide webhooks. Switching a webhook on (also after it switched off by itself) makes the connected user the person behind it. Setting a URL on an organisation-wide webhook (even its current one) moves it to the active workspace: from then on it receives only that workspace's events (get_webhook shows the new scope; an organisation-wide webhook is made in the OmniSocials dashboard).
Inputs: id (required), url, events, is_active.
upload_mediaAInspect
Upload media to the library. Three methods supported:
url — import from a PUBLIC https URL (e.g. a hosted image link). NEVER pass a local sandbox path — the URL must be reachable from our servers.
base64_data — pass base64-encoded file data directly. ONLY use this for tiny files (≲50 KB). MCP tool inputs are token-capped — anything larger gets silently truncated and uploads a corrupted file. For any user-pasted image, use upload_url instead.
upload_url — PREFERRED for any file the user attached to the chat. Call with method="upload_url" to get a one-time presigned URL plus a ready-to-run snippet. Execute the snippet in your code-execution tool against the actual file path. The response JSON contains the media id you pass to create_post.
Size limits: base64/direct uploads are capped at 100 MB. For anything larger — up to 1 GB — use a public url (fetched server-side, bypasses the cap), OR have the user upload the file in the OmniSocials Library UI at https://app.omnisocials.com/library . IMPORTANT: if the user has a large LOCAL file (over ~100 MB) with no public url, do NOT tell them to compress it — point them to the Library UI link above. Large videos (over 100 MB) are processed in the background — the response status is "processing" and the file is NOT usable in a post until it becomes "ready" (re-check with list_media).
Limits during the upload (100 MB or less): a video whose picture is not H.264 (HEVC, AV1, VP9 and others) is converted to H.264 MP4, and that conversion refuses a video longer than 10 minutes or larger than 4096x2304, and all video work of one upload stops after about 50 seconds (error video_transcode_failed; the message says which). Relay the message: the user exports the video as an H.264 MP4 and uploads it again. When the server is converting other videos and no slot frees within a minute, the upload answers 503 video_busy with Retry-After: the file is fine, send the same upload again after that wait. A PDF whose page or embedded image is too large to turn into slides answers pdf_too_large: ask for an export at a normal page size.
Compatibility: every upload response includes a "compatibility" summary of any CONNECTED platforms that would reject the file (e.g. too large for Instagram). If there are warnings, RELAY them and ask the user whether to continue before posting — the file still uploads and can post to platforms that accept it. To check BEFORE uploading, call check_media_compatibility first.
PDF = carousel: upload a PDF (via a public url, or base64_data with mime_type "application/pdf", or the upload_url snippet) and it is split into one image slide per page (max 20). The response lists a Media ID for EVERY slide — pass ALL of them, in order, as media_ids to create_post to post the deck as a carousel. On LinkedIn the slides post as a native swipeable DOCUMENT made from the ORIGINAL PDF file (the file is kept: text stays sharp, in-document links work, viewers download the real file, and every page is included even past the 20-slide cap) as long as the slides are posted unchanged and in order; on Instagram, TikTok, Threads and Pinterest as an image carousel. Set linkedin.document_source to 'slides' on the post to send a document rebuilt from the slide images instead. This is how a user posts an existing slide deck (Canva/PowerPoint/Figma exported to PDF) as a carousel. Prefer pdf_mode "document" when the user wants ONE library item for the deck (no per-page clutter): the response then has a single Media ID whose media_ids entry expands into every page at post time.
Supported: JPEG, PNG, GIF, WebP, MP4, MOV, AVI, PDF.
For user-attached files: ALWAYS try upload_url first. Call upload_media with method="upload_url", then in your code-execution sandbox run the returned Python (ChatGPT Code Interpreter, file at /mnt/data/) or curl (Claude Code Execution) snippet against the actual file path. Only react to a failure AFTER actually executing the snippet.
Inputs: url, file, name, folder, +5 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs112 npm46 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.