MCP Tools Reference
Every tool the SociaHive MCP server exposes — parameters, required API-key scopes, feature flags, and confirmation requirements.
The SociaHive MCP server advertises 87 tools (33 read, 51 write, 3 destructive). Every one runs through the same chokepoint the in-app copilot uses, so auth, tier limits, rate limits, credits, and audit logging apply identically whether the caller is Claude Desktop, the CLI, or the dashboard.
Connect a client first — see the setup guide.
How access is decided
A tool call has to clear four gates, in order:
- API key +
agent:execute— enforced at/api/mcpbefore the server is reached. - Per-tool scopes — the "Required scopes" column below. A key with
*clears all of them. - Feature flag — tools in the "Notes" column with a
flag:entry are inert unless that flag is on for your account. Most follow your plan; a few are still admin-only previews. - Confirmation — tools marked
confirmare irreversible or reach outside SociaHive. The first call returns apending_confirmationenvelope with a token; call again passing__confirmToken. With an API key (CLI, SDK, MCP with ansk_key) you can instead passconfirm: truewhere the tool accepts it. Apps connected with OAuth (ChatGPT, Claude and other AI apps you sign in to) cannot useconfirm: true, starting now: they confirm with the token two-step after the person agrees. From 2026-11-09 SociaHive asks the person directly, in the app's own approval prompt or on an approval page in SociaHive, and the app never receives a token.
Tools marked not on connect keys need a scope the one-click Connect to AI key doesn't carry. Mint a key with the scopes you need in Settings → API Keys.
Tool groups
Tools come in groups. Every client gets every tool when it connects. Claude and ChatGPT keep a long tool list out of the model's context on their own (tool search), so nothing needs to be loaded first.
To start with a shorter list, choose groups when you connect:
- Add
?toolsets=a,bto the server URL (https://www.sociahive.com/api/mcp?toolsets=analytics,growth) or send the headerX-MCP-Toolsets: analytics,growth. You get thecoregroup, those groups, and two more tools:list_toolsetsreturns the groups, what each is for, their tools and which are loaded;enable_toolsetwith{ "name": "<group>" }loads one more group and returns its tools, so they can be called even in a client that does not refresh its tool list.?toolsets=allgives every tool. - A tool that is not in the list can still be called by name, with the same scopes, plan limits and confirmations.
| Group | Tools |
|---|---|
core | whoami, list_accounts, list_capabilities, get_capabilities, create_scheduled_post, get_scheduled_post, list_scheduled_posts, get_scheduler_calendar, update_scheduled_post, cancel_scheduled_post, publish_post_now, arm_post_automation, request_media_upload, finalize_media_upload, upload_media_from_url, list_published_media, list_flows, get_flow, generate_flow, generate_multiple_flows, create_flow, activate_flow, deactivate_flow, publish_flow_changes, get_analytics_overview |
flows-advanced | add_node, update_node, delete_node, add_edge, update_edge, delete_edge, create_youtube_comment_flow, update_flow, bulk_update_flows, duplicate_flow, restore_flow, discard_flow_changes, get_flow_revisions, revert_flow_to_version, summarize_flow_purpose, list_system_templates, get_collected_data, create_automation |
scheduler-advanced | schedule_post, publish, bulk_reschedule_posts, duplicate_scheduled_post, restore_scheduled_post, add_posting_slot, update_posting_slot, delete_posting_slot, list_posting_slots, find_next_slot, create_signature, list_signatures, list_rss_feeds, update_rss_feed, add_to_evergreen, list_evergreen, add_post_milestone_action, list_post_milestone_actions, list_account_destinations, list_pinterest_boards, detach_post_automation |
media | list_media, generate_post_image |
analytics | get_post_analytics, get_flow_stats, get_content_insights, get_post_link_clicks, get_pixel_embed |
growth | create_ref_url, create_broadcast, create_sequence, create_landing_page, create_growth_widget, create_tag, search_tags, capture_lead, resolve, find_references |
agency | create_client_invite, list_client_invites, create_review_link, list_review_links |
admin-bulk | delete_flow, delete_scheduled_post, bulk_delete_scheduled_posts |
Tools
Session & capability
| Tool | What it does | Parameters | Required scopes | Notes |
|---|---|---|---|---|
whoami | Use this when the user asks who they are signed in as, which plan they are on, or which account is selected. | — | — (no scope) | — |
list_capabilities | Use this when the user asks what SociaHive can do from here. | — | — (no scope) | — |
Flows — read
| Tool | What it does | Parameters | Required scopes | Notes |
|---|---|---|---|---|
list_flows | Lists the user's automation flows: id, name, status, trigger type, platform, updatedAt, createdAt. | mode, query, metric, status, limit, sortBy, sortOrder, cursor, accountId, accountIds, platform | flows:read | pass accountId on multi-account keys |
get_flow | Returns one flow: its steps, each step's outputs (buttons and branches, with the step each connects to), its connections with their ids, anything that stops it running, and the state of its AI build (building, needs_clarification, failed... | flowId, nodeId, version | flows:read | — |
summarize_flow_purpose | Returns a one-sentence summary of a flow's purpose plus its source (client-side sampling or server-side fallback). | flowId | flows:read | — |
get_flow_stats | Returns execution analytics for one flow: total triggers, button clicks, unique users, status breakdown and a daily timeline for the last 7 days. | flowId | flows:read | — |
get_collected_data | Summarizes the data a flow collected: total count, breakdown by field type and the last N submissions. | flowId, fieldType, limit | flows:read | — |
list_system_templates | Lists SociaHive's pre-built flow templates, such as welcome messages, lead generation and customer support, with names and descriptions. | category, limit, cursor | flows:read | — |
get_flow_revisions | Lists the version history of a flow: the most recent N revisions (default 50, max 200), newest first. | flowId, limit | flows:read | — |
find_references | Lists the flows that reference a tag, for example in conditions or tag actions. | entityType, entityId, limit | flows:read tags:read | — |
Flows — write
| Tool | What it does | Parameters | Required scopes | Notes |
|---|---|---|---|---|
activate_flow | Use this when the user wants a flow live ("publish flow X", "turn on the welcome DM"). | flowId, flowName, confirm | flows:write | confirm |
deactivate_flow | Unpublish (deactivate) a flow so it stops processing triggers. | flowId, flowName | flows:write | — |
duplicate_flow | Copy an existing flow as a new draft. | flowId, flowName, newName | flows:write | — |
update_flow | Use this when one flow is renamed or its description changes ("rename this flow to X"). | — | flows:write | — |
create_flow | Creates a new empty automation flow as a draft, with no nodes or edges, for a connected account (by @handle or id); the flow takes the account's platform. | name, description, accountId, platformUserId, platform, trigger | flows:write | — |
generate_flow | Use this when the user describes one automation to build ("when someone comments PRICE, DM them the link", "a welcome DM for new followers"). | description, platform, variants, iterateOnFlowId, businessContext, accountId, allowFollowGate, name | flows:write | flag: AI_FLOW_BUILDER |
add_node | Adds a node to a flow's graph. | flowId, flowName, type, position, name, data, allowFollowGate | flows:write | — |
update_node | Changes one existing node in a flow. | — | flows:write | — |
add_edge | Connects two steps of a flow. | flowId, flowName, source, target, sourceHandle, targetHandle, type, data | flows:write | — |
update_edge | Sends an existing connection of a flow to another step. | flowId, flowName, edgeId, source, sourceHandle, target, newTarget | flows:write | — |
delete_node | Removes a single node from a flow, along with every edge that referenced it. | flowId, flowName, nodeId | flows:write | — |
delete_edge | Removes a single connection from a flow, named by flowId or flowName. | flowId, flowName, edgeId, source, sourceHandle, target | flows:write | — |
bulk_update_flows | Use this when several flows change at once ("rename the holiday flows"). | flowIds, filter, patch | flows:write | — |
revert_flow_to_version | Reverts a flow to a previous version. | flowId, targetVersion | flows:write | — |
publish_flow_changes | Puts the unpublished changes of a live flow live, after the same checks as turning a flow on. | flowId, flowName, expectedRev, confirm | flows:write | confirm, flag: FLOW_PENDING_VERSIONS |
discard_flow_changes | Drops the unpublished changes of a live flow; people keep getting the live version as it is. | flowId, flowName, expectedRev, confirm | flows:write | confirm, flag: FLOW_PENDING_VERSIONS |
create_youtube_comment_flow | Creates a YouTube comment automation as a draft for a connected YouTube account (by @handle or id): it replies publicly to comments on the channel's videos and Shorts, on every comment or only those containing a keyword, on every video (... | accountId, name, description, keywords, videoIds, replies, replyDelaySeconds, postCapPerHour, postCapPerDay, postCapTotal | flows:write | flag: YOUTUBE_COMMENT_AUTOMATION |
create_automation | Builds a draft automation from an outcome sentence for a connected account given by its id, and returns a plain-language preview. | outcome, accountId | flows:write | flag: OUTCOME_API_TOOLS |
generate_multiple_flows | Use this when one message asks for several automations at once, including migrating or rebuilding a whole setup from another tool ("rebuild my whole ManyChat account on here", "price comments get the pricing DM, guide comments collect an... | description, accountId, allowFollowGate | flows:write | confirm, flag: AI_BULK_FLOW_GENERATION |
Posts & scheduler — read
| Tool | What it does | Parameters | Required scopes | Notes |
|---|---|---|---|---|
list_scheduled_posts | Use this when the user asks about posts in the SociaHive scheduler: drafts, queued, recurring, failed, or posts that went out through the scheduler ("what's scheduled this week", "show my drafts", "what posts went out yesterday", "my mos... | status, platform, accountId, limit, sortOrder, cursor | posts:read | — |
get_scheduled_post | Returns one scheduler-side post by id (draft, queued, recurring or published via the scheduler): full text, recurrence, status detail, each platform's result (status, the error when it failed, the live link, its format, the platform opti... | postId | posts:read | — |
get_scheduler_calendar | Use this when the user asks for a calendar view of a date range ("show my calendar for next week"). | range, fromDate, toDate, platform | posts:read | — |
get_post_analytics | Returns per-platform analytics for one published post: impressions, reach, engagement, likes, comments, shares, saves and clicks, one row per platform target, with avgWatchTimeSeconds and totalWatchTimeSeconds for an Instagram Reel, and ... | postId | posts:read | — |
get_analytics_overview | Returns aggregate analytics across all published posts: total impressions, total engagement, post count, a per-platform breakdown and a 30-day timeline. | startDate, endDate, platform | posts:read | — |
list_evergreen | Lists the evergreen queue: recyclable posts that fill failed Autopilot slots. | — | posts:read | flag: SCHEDULER_EVERGREEN |
Posts & scheduler — write
| Tool | What it does | Parameters | Required scopes | Notes |
|---|---|---|---|---|
schedule_post | Use this when the user wants an existing draft on the publishing calendar ("schedule this for Tuesday at 9am"). | postId, postName, scheduledAt, timezone, attach_automation, attach_funnel | posts:write | — |
update_scheduled_post | Use this when an existing post changes: text, media (replaces all), time or timezone, including rescheduling ("reschedule the launch announcement for friday", "move it to Monday"). | — | posts:write | — |
cancel_scheduled_post | Cancels a scheduled post by reverting it to a draft. | postId, postName | posts:write | — |
publish_post_now | Publishes a post immediately to all its configured platforms. | postId, postName | posts:write | confirm |
create_scheduled_post | Use this when the user wants a new post from content they supply, as a draft or scheduled in the same call. | text, media, platforms, scheduledAt, timezone, signatureId, nextSlot | posts:write | — |
bulk_reschedule_posts | Moves up to 50 scheduled posts to a new publish time (scheduledAt, ISO 8601) in one call. | postIds, scheduledAt, timezone | posts:write | — |
publish | Publish a prepared post (by postId) to its platforms immediately. | postId, platforms | posts:write | confirm, flag: OUTCOME_API_TOOLS |
add_to_evergreen | Adds a recyclable post (caption text) to the evergreen queue. | text, sourcePostId | posts:write | flag: SCHEDULER_EVERGREEN |
Accounts & media
| Tool | What it does | Parameters | Required scopes | Notes |
|---|---|---|---|---|
list_accounts | Use this when the user asks which social accounts are connected, or whether a platform is connected. | platform, status | accounts:read | — |
list_pinterest_boards | Boards of the user's Pinterest accounts. | accountId | posts:read | — |
list_published_media | Lists media published on the user's connected platform (Instagram first). | mode, id, query, mediaType, limit, accountId | accounts:read | pass accountId on multi-account keys |
get_capabilities | Lists what each connected account can do: automation (DM and comment triggers, and comment replies on YouTube) and scheduling (posts). | accountId | accounts:read | — |
resolve | Auto-resolve a support conversation (by sessionId) from the knowledge base. | sessionId, message | accounts:write | flag: OUTCOME_API_TOOLS, not on connect keys |
capture_lead | Capture a lead: find-or-create a contact from (platform, platformUserId) and record a lead-outcome. | platform, platformUserId, source, username, displayName | accounts:write | flag: OUTCOME_API_TOOLS, not on connect keys |
Content insights
| Tool | What it does | Parameters | Required scopes | Notes |
|---|---|---|---|---|
get_content_insights | Returns the account's content performance insights: which formats, days of the week and content pillars index above or below the account's average engagement (with sample sizes), plus top and bottom posts. | weeks | analytics:read | flag: SCHEDULER_LEARNING_LOOP |
Tags
| Tool | What it does | Parameters | Required scopes | Notes |
|---|---|---|---|---|
search_tags | Resolve tag reference ("tagged X"). | query, limit | tags:read | — |
create_tag | Creates a tag. | name, color | tags:write | — |
CRM & growth
| Tool | What it does | Parameters | Required scopes | Notes |
|---|---|---|---|---|
create_broadcast | Creates a one-time broadcast as a draft. | name, channel, message, audience | broadcasts:write | confirm, flag: AI_MAIN_FEATURE_TOOLS |
create_sequence | Creates a drip sequence as a draft. | name, description, steps | sequences:write | confirm, flag: AI_MAIN_FEATURE_TOOLS |
create_landing_page | Creates a hosted lead-capture landing page as a disabled draft, not public until a person enables it. | name, headline, body, button_text, slug | growth_tools:write | confirm, flag: AI_MAIN_FEATURE_TOOLS |
create_growth_widget | Creates a website growth widget (popup, slide-in, bar or embed box) as a disabled draft, for signup popups, announcement bars and embedded capture boxes. | name, widget_type, headline, body, button_text | growth_tools:write | confirm, flag: AI_MAIN_FEATURE_TOOLS |
create_ref_url | Use this when the user wants a tracked link that counts clicks: a link-in-bio link, or a referral or invite link ("a tracked link for my tiktok bio", "a referral link so each invite gets counted"). | name, flow_id, platform, messageText, plainCode | growth_tools:write | flag: AI_MAIN_FEATURE_TOOLS |
get_pixel_embed | Returns the account's SociaHive Pixel install snippet and setup steps, for tracking events on a website. | — | analytics:read | flag: AI_MAIN_FEATURE_TOOLS |
Delete and restore
| Tool | What it does | Parameters | Required scopes | Notes |
|---|---|---|---|---|
delete_flow | Archives a flow (status 'archived'). | flowId, flowName | flows:write agent:destructive | confirm, flag: AI_COPILOT_DESTRUCTIVE_TOOLS, not on connect keys |
delete_scheduled_post | Deletes a scheduler post: it is hidden from all dashboards and will not publish. | postId, postName | posts:write agent:destructive | confirm, flag: AI_COPILOT_DESTRUCTIVE_TOOLS, not on connect keys |
bulk_delete_scheduled_posts | Soft-deletes up to 50 scheduler posts in one call. | postIds, filter | posts:write agent:destructive | confirm, flag: AI_COPILOT_DESTRUCTIVE_TOOLS, not on connect keys |
restore_flow | Restores a deleted flow from the trash as a draft. | flowId, flowName | flows:write | flag: AI_COPILOT_DESTRUCTIVE_TOOLS |
restore_scheduled_post | Restores a deleted scheduler post. | postId, postText | posts:write | flag: AI_COPILOT_DESTRUCTIVE_TOOLS |
Other
| Tool | What it does | Parameters | Required scopes | Notes |
|---|---|---|---|---|
list_media | Lists the images and videos uploaded to the scheduler (the media library), newest first. | kind, tag, query, limit, cursor | posts:read | flag: SCHEDULER_MEDIA_LIBRARY |
list_post_milestone_actions | List a post's milestone actions (called plugs in the app): "when this post gets 100 likes, repost it / add this comment". | postId | posts:read | flag: SCHEDULER_PLUGS |
list_review_links | List the client review links of a post and what the client said ("did my client approve Tuesday's post?"). | postId, postName | posts:read | flag: SCHEDULER_CLIENT_REVIEW_LINK |
get_post_link_clicks | Clicks on the short links of a scheduled or published post. | postId | posts:read | flag: SCHEDULER_SHORT_LINKS |
list_signatures | List the user's saved post signatures (sign-offs appended after a blank line when a post publishes). | — | posts:read | flag: SCHEDULER_SIGNATURES |
find_next_slot | Look up the next free posting slot for a post on these accounts: the earliest of their weekly posting times (next 60 days) where none of them already has a scheduled post within 5 minutes. | accountIds, after | posts:read | flag: SCHEDULER_POSTING_SLOTS |
list_client_invites | List the user's client invite links ("did my client connect their accounts?"): state, how many accounts each added and which ones. | groupId | accounts:read | flag: SCHEDULER_CLIENT_INVITE_LINK |
list_rss_feeds | List the user's RSS feeds (at most 5) and how each new item is handled: "draft" (a draft of the item's text), "ai_draft" (AI writes a draft for review) or "ai_schedule" (AI writes it and schedules it into the next free posting slot). | — | posts:read | flag: SCHEDULER_RSS_AI |
list_account_destinations | Destinations (channels, communities) of one connected account; input checks one the user named. | accountId, input, fresh | posts:read | flag: CONTENT_SCHEDULER |
arm_post_automation | Turns on "Turn on when this post goes live" for the comment automation attached to a scheduled post, so the automation goes live with the post. | postId, postName, confirm, contentHash | posts:write flows:write | confirm, flag: MCP_ARM_POST_AUTOMATION |
detach_post_automation | Removes the automation from a scheduled post. The post is unchanged and goes out as scheduled; an automation that is already live stays live. | postId | posts:write flows:write | confirm |
upload_media_from_url | Copy an image, video or PDF into the user's SociaHive uploads and return a URL on our storage: from a public URL, or in ChatGPT from the conversation (an image ChatGPT made or one the user added). | url, or file (ChatGPT) | uploads:write | confirm, flag: MEDIA_UPLOAD_FROM_URL |
request_media_upload | Starts direct uploads of image, video or PDF files into the user's SociaHive uploads and returns a URL for an HTTP PUT of each file. | fileName, mimeType, sizeBytes, files | uploads:write | flag: MCP_PRESIGNED_UPLOAD |
finalize_media_upload | Finishes direct uploads started with request_media_upload, once each file was sent with PUT: checks the stored file and returns its URL on SociaHive storage. | uploadId, fileName, uploads, addToMediaLibrary | uploads:write | flag: MCP_PRESIGNED_UPLOAD |
create_review_link | Make a client review link for a scheduled post or draft ("send this post to my client for approval"). | postId, postName, reviewerName | posts:write | confirm, flag: SCHEDULER_CLIENT_REVIEW_LINK |
duplicate_scheduled_post | Copies a post as a new draft with the same text, media, channels, platform options and tags. | postId, postName | posts:write | flag: SCHEDULER_CALENDAR_CARD_ACTIONS |
add_post_milestone_action | Add a milestone action (called a plug in the app) to a scheduled or published post: when it reaches threshold of metric on that account, SociaHive reposts it (X) or adds the comment, once. | postId, accountId, metric, threshold, action, text | posts:write | confirm, flag: SCHEDULER_PLUGS |
generate_post_image | Makes 1 to 4 AI images for a post from a description (prompt) or from the post caption (caption). | prompt, caption, aspect, count | uploads:write | flag: SCHEDULER_COMPOSER_IMAGE_GEN |
create_signature | Save a post signature (a sign-off such as "Team Acme · acme.com") the user can append to posts at publish. | name, text, accountIds, isDefault | posts:write | flag: SCHEDULER_SIGNATURES |
list_posting_slots | List the user's posting slots: weekly posting times per account ("every Monday at 09:30, Europe/Berlin, for @shop"). | accountIds | posts:read | flag: SCHEDULER_POSTING_SLOTS |
add_posting_slot | Add a weekly posting slot for some accounts, e.g. | accountIds, weekday, time, timezone | posts:write | flag: SCHEDULER_POSTING_SLOTS |
update_posting_slot | Change a posting slot's accounts, weekday, time or time zone. | slotId, accountIds, weekday, time, timezone | posts:write | flag: SCHEDULER_POSTING_SLOTS |
delete_posting_slot | Delete a posting slot. | slotId | posts:write | flag: SCHEDULER_POSTING_SLOTS |
create_client_invite | Make a client invite link for one of the user's account groups ("send my client a link to connect their Instagram"). | groupId, groupName, platforms, maxAccounts | accounts:write | confirm, flag: SCHEDULER_CLIENT_INVITE_LINK, not on connect keys |
update_rss_feed | Pause or resume an RSS feed, or change how AI writes posts from it: mode ("draft" or "ai_draft"), instructions, tone, image, accounts and the daily cap. | feedId, paused, mode, instructions, tone, image, accountIds, dailyCap | posts:write | flag: SCHEDULER_RSS_AI |
Follow check ("Ask to follow")
generate_flow and add_node can build an "Ask to follow" step: the flow continues
only once Instagram confirms the person follows the account. It is built only when your
user asked for it, never on the assistant's own initiative, and only on Instagram flows of
accounts that have the step. Over MCP and the API, pass allowFollowGate: true: on
generate_flow the description must also say that people must follow first ("only send
the guide to people who follow me"); on add_node use type: "follow_gate". The step's
messages are the product defaults, which the user can change in the flow editor. Without
the flag, or when the description does not ask, the flow is built without it.
Comment trigger settings
An Instagram post or reel comment trigger keeps its public reply settings in its config. Set
them with update_node on the trigger step, as data: { triggers: [{ config: { ... } }] }.
Only the keys you send change; the others are kept.
| Key | What it does |
|---|---|
comment_reply_enabled | true to reply publicly under the comment. |
comment_reply_templates | The reply texts, up to 2,200 characters each. With several, they take turns on each post: the first comment on a post gets the first text, the next comment the second, and after the last text it starts again. Each trigger keeps its own turn on each post. |
comment_reply_only | true to reply publicly and send no DM. |
comment_reply_timing | Kept for older flows and not used: the public reply goes out after the first DM, or right away on a reply-only trigger. |
comment_reply_post_cap_per_hour | At most this many public replies on one post in a clock hour, a whole number from 1 to 1000. null removes it. |
comment_reply_post_cap_per_day | At most this many public replies on one post in 24 hours, a whole number from 1 to 1000. The 24 hours start at the first counted reply; when they end, replies resume by themselves. null removes it. |
comment_reply_post_cap_total | At most this many public replies on one post overall, a whole number from 1 to 1000. null removes it. |
comment_reply_disabled_media_ids | Posts (platform media ids, at most 100, each up to 100 characters) where this trigger sends no public reply. DMs still go. null switches public replies back on. |
A cap outside 1 to 1000, or not a whole number, and a bad list of post ids are refused with a validation_error that
names the key. Over a cap the public reply is skipped and the DM still goes; a reply-only
trigger then sends nothing. The caps count the comment reply and keyword replies, and are
shared by every flow that replies on that post.
On a live flow (published or paused), update_node saves the change as an unpublished
change and people keep getting the live version. To stop the public replies on a live
flow and keep the DMs:
update_nodeon the trigger step withdata: { triggers: [{ config: { comment_reply_enabled: false } }] }. The answer haspendingChanges: true.publish_flow_changeswithconfirm: trueand noexpectedRev: the preview lists the changed trigger and returnsrev.- After the person agrees,
publish_flow_changeswithconfirm: trueandexpectedRevset to thatrev. From then on new comments get the DM and no public reply.discard_flow_changesdrops the change instead.
YouTube comment automations
A YouTube comment automation replies publicly to comments on the channel's videos and
Shorts. YouTube has no DMs, so the reply is the whole automation: the flow is one trigger
step with no other steps. generate_flow and create_flow do not build it;
create_youtube_comment_flow does, as a draft:
keywords: reply only to comments containing one of them. Omit for every comment.videoIds: video or Short ids, or their links. Omit for every video and Short, new ones included.replies: 1 to 10 reply texts, up to 10,000 characters each. With several, they take turns on each video.replyDelaySeconds: 0, 60, 300, 900, 1800 or 3600.postCapPerHour,postCapPerDay,postCapTotal: per-video reply limits, as in the table above.
It is created off. activate_flow turns it on after the same checks as the editor; the
answer's warnings list anything that would stop that. Find it later with list_flows
and platform: "youtube". To change it, update_node on its trigger step with
data: { triggers: [{ config: { ... } }] }, using the keys of the table above plus
keywords, reaction_type ("keyword" or "any"), comment_reply_delay_s and
media_ids. To change the videos, send media_ids together with select_all_posts and
select_all_future (true with an empty list for every video, false with ids).
get_capabilities lists automation for YouTube when the account can use it.
Resources
Read-only context the client can fetch by URI, no tool call needed. Eleven are listed
by resources/list; the two templated URIs are readable but not enumerated.
| URI | Contents |
|---|---|
sociahive://platforms | Supported platforms and their capabilities |
sociahive://trigger-types | Flow trigger types per platform |
sociahive://node-types | Flow node types |
sociahive://post-statuses | Scheduled-post status machine |
sociahive://flows | Your flows |
sociahive://posts/upcoming | Next 14 days of scheduled posts |
sociahive://accounts | Your connected accounts |
sociahive://audit/recent | Recent agent actions taken on your account |
sociahive://health | Account health signals |
sociahive://changelog | Platform changelog |
sociahive://docs/quick-start | Quick-start guide |
sociahive://flows/{id} | One flow, full detail (template — not listed) |
sociahive://posts/{id} | One scheduled post (template — not listed) |
Clients that support notifications/resources/updated get pushed refreshes when a post
publishes or a flow changes.
Prompts
One-click workflows the client surfaces as slash commands.
| Prompt | Arguments | What it does |
|---|---|---|
weekly-report | timezone | Reads upcoming posts + flow stats, writes a Monday recap |
content-audit | lookback_days | Reviews scheduled posts for tone, clashes, platform-fit |
flow-cleanup | — | Finds inactive/underperforming flows, proposes archives |
onboard-agency | client_name, platforms | Scaffolds a new agency client's flows and draft posts |
Known gaps
A live audit on 2026-08-20 found six defects here. All are now fixed; this section records what remains.
- Scope catalog: no gaps. Every scope enforced at a chokepoint is mintable on a granular key, guarded by
api-key-scope-catalog.test.ts. - 6 tools are unreachable from a one-click connect key — they need scopes outside the connect grant (deliberately: the connect key is fixed and non-destructive). Mint a custom key with the scopes you need.
- 2 tools need an explicit
accountIdon a multi-account key. MCP keys are workspace-level with no account picker, so a default account is bound only when the owner has exactly one. On a key with two or more, passaccountId(fromlist_accounts) tolist_flows,list_published_media. Omitting it returnsauth_error / no_account_selected; an id you don't own returns the same error rather than leaking that it exists. - Deletes need
agent:destructiveand a confirmation.delete_flow,delete_scheduled_postandbulk_delete_scheduled_postsneedagent:destructiveplusflows:writeorposts:write, and run only after a confirmation. A connected AI app can delete up to 50 items a day, at most 10 deletes in 10 minutes, and the account owner is notified. Deleted flows stay in the trash for 30 days:restore_flowandrestore_scheduled_postbring them back.DELETE /api/v1/posts/{id}performs the same soft-delete withposts:write.
Errors and limits
Typed error envelopes and retry guidance: errors · rate limits.