activate_flow
ChatGPTPublish (activate) a flow so it processes triggers in production. "publish flow X", "turn on the welcome DM", "activate this". Identify it by flowName — its name is enough, no id lookup. Surfaces keyword conflicts with other published flows as advisory warnings; relay them.
add_edge
ChatGPTConnect two nodes in a flow with an edge. Use sourceHandle for button connections (e.g., "button-0" wires the first button on a message node). Edges define the flow execution path. Use when the user says "connect the welcome message to the discount step" / "wire button 1 to the next node". Rejects mutations against published flows.
add_node
ChatGPTAdd a node to a flow's graph. Node types: platform message nodes (instagram, whatsapp, messenger, twitter, linkedin, telegram, tiktok), delay (wait), condition (branch), data_collection (collect input), ai_response (AI reply), action (tag/notify), comment (reply to comment), webhook (HTTP call), randomizer (A/B), ai_step (multi-turn AI), follow_gate ("Ask to follow", Instagram, only if the user asked). Use during conversational flow building ("add a delay between the welcome and the discount"). Rejects mutations against published flows — duplicate first.
add_post_milestone_action
ChatGPTAdd 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. Posts to a real audience when it fires, so it requires confirmation. Max 3 per account on a post, 10 watching per user.
add_posting_slot
ChatGPTAdd a weekly posting slot for some accounts, e.g. every Monday at 09:30 Europe/Berlin. The time is a wall-clock time in the slot's zone and stays put across daylight-saving changes. Nothing is published. Up to 100 slots per user.
add_to_evergreen
ChatGPTAdd a recyclable post (caption text) to the user's evergreen queue. Use for "save this as evergreen" / "recycle this post". Items fill failed Autopilot slots later, always through review — adding never publishes anything.
bulk_delete_scheduled_posts
ChatGPTSoft-deletes up to 50 scheduler posts in one call. The set is either a filter {status, nameContains}, which the server expands to the matching posts, or explicit postIds. Requires one confirmation that names the resolved posts; nothing is deleted before it. Scheduler-side only: posts already published stay live on the platform. Returns a result per post.
bulk_reschedule_posts
ChatGPTMove up to 50 scheduled posts to a new publish time in one call. Use when the user says "push all Friday's posts to Monday" or similar. Per-post failures (already-published, in-flight, deleted) are reported in the results array but don't block the rest. Pass scheduledAt as ISO 8601.
bulk_update_flows
ChatGPTBatch-edit up to 50 flows in ONE call — every PLURAL flow edit ("rename the holiday flows"). FIRST call: describe the set with filter {status, nameContains} and the server expands it; pass explicit flowIds only when you already hold them. Never fan out per-flow tools, never list first. Patches identity fields (name, description) only — not graph or status. Per-item results; partial failures don't abort the rest.
cancel_scheduled_post
ChatGPTCancel a scheduled post — reverts to draft so it won't publish. "cancel that scheduled post", "don't publish Tuesday's post". Identify it by postName (its caption / opening words) when you have no id. Idempotent: already-draft posts return success unchanged.
capture_lead
ChatGPTCapture a lead: find-or-create a contact from (platform, platformUserId) and record a lead-outcome. Idempotent (no double-count).
create_automation
ChatGPTDraft an automation from a natural-language outcome. Returns a DRAFT + preview; never goes live.
create_client_invite
ChatGPTMake a client invite link for one of the user's account groups ("send my client a link to connect their Instagram"). The client opens it without a SociaHive account, connects their own Facebook, Instagram, LinkedIn, Pinterest or X accounts on each platform's consent screen, and the accounts land in that group. Each account counts toward the plan's account limit. Works for 7 days. The URL is returned once.
create_flow
ChatGPTCreate a new empty automation flow as a draft. Use when the user wants to start from scratch ("make a new flow", "I want to build a flow for X"). The flow has no nodes/edges yet — use add_node and add_edge to build it, or call generate_flow instead to have AI build it from a description. Trigger config is optional; if omitted the user picks one in the canvas.
create_review_link
ChatGPTMake a client review link for a scheduled post or draft ("send this post to my client for approval"). The client opens it without an account, sees the post as each platform shows it, comments, and approves or asks for changes. Approving never schedules or publishes. Works for 14 days. The URL is returned once.
create_scheduled_post
ChatGPTCreate a NEW social post from supplied content — draft, optionally scheduled in the same call. Use whenever the post does not exist yet: "draft a post about X", "schedule a post saying '<text>' tomorrow 9am", "queue a post about our launch for monday". FIRST call, always: platforms takes just the platform NAME ({platform:"instagram"}) — the server resolves the connected account, so NEVER call list_accounts first — and scheduledAt takes the user's own words ("tomorrow 9am", "next monday") or ISO; omit it for a pure draft. To publish RIGHT NOW: this tool, then publish_post_now. For an EXISTING draft use schedule_post.
create_signature
ChatGPTSave a post signature (a sign-off such as "Team Acme · acme.com") the user can append to posts at publish. With isDefault it is added to every post on its accounts unless a post picks another signature or "none"; saving a default turns off the default it replaces. At most 20 per user. Saves a setting; nothing is posted.
current_page_context
ChatGPTReturns what the user is looking at — route, entity type/id/name, selection. Use ONLY when they ask what page they are on, or when the <page_context> block in your instructions reads "(none …)". When <page_context> already names an entity this returns the SAME data — it wastes the turn; never call it before editing or deleting that entity.
deactivate_flow
ChatGPTUnpublish (deactivate) a flow so it stops processing triggers. "pause this flow", "stop the welcome DM", "unpublish". Identify it by flowName — its name is enough, no id lookup. Idempotent: already-draft flows return success unchanged.
delete_edge
ChatGPTRemove a single edge (connection) from a flow. The nodes themselves stay; only the wiring between them is removed. Use when the user says "disconnect the welcome from the discount" / "remove the link to the followup". Rejects mutations against published flows.
delete_flow
ChatGPTArchives a flow (status 'archived'). The flow is identified by flowName (its name) or flowId. Requires confirmation. The flow stays in the trash for 30 days; restore_flow brings it back as a draft. Rejects flows in 'publishing' state.
delete_node
ChatGPTRemove a single node from a flow. Cascades: the underlying remove drops every edge that referenced the node, so the artifact card re-renders cleanly. Use when the user says "remove the email collection step" / "delete the followup message". Rejects mutations against published flows. NOTE: this is delete_node (one node), not delete_flow (the whole flow) — those are different tools.
delete_posting_slot
ChatGPTDelete a posting slot. Posts already scheduled into it keep their times; nothing is published or unpublished.
delete_scheduled_post
ChatGPTDeletes a scheduler post: it is hidden from all dashboards and will not publish. Soft delete: the SociaHive record is marked deleted and its pending publish jobs are cancelled; restore_scheduled_post brings it back. Scheduler-side only: a post already published stays live on the platform, and published media on platforms is not deleted. Requires confirmation. Rejects posts in 'publishing' state.
discard_flow_changes
ChatGPTDrops the unpublished changes of a live flow; people keep getting the live version as it is. Use this when the person no longer wants the changes made to a live flow, or when the live version changed since they were made. Two steps: a call with confirm: true and no expectedRev returns the preview (steps added, changed and removed, who made the changes, and rev) without discarding; after the person has seen it and agreed, a call with confirm: true and expectedRev set to that rev discards. A rev that no longer matches the changes is refused. The dropped changes are kept as a version that never went live, and can be restored from the flow in SociaHive while it is kept.
duplicate_flow
ChatGPTCopy an existing flow as a new draft. "duplicate flow X", "clone the giveaway flow". Identify the source by flowName; newName names the copy. The copy starts in draft — edit + publish separately.
duplicate_scheduled_post
ChatGPTCopy a post as a new DRAFT with the same text, media, channels, platform options and tags ("duplicate Tuesday's post", "make a copy of that post"). The copy has no time: schedule it afterwards with schedule_post. Never copies publish results, the comment automation or review links. Identify the post by postName (its caption or opening words) when you have no id.
finalize_media_upload
ChatGPTFinishes 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. One upload is given as uploadId; several (up to 25) are given as uploads, each with an optional fileName, and the result then has items in the order given, while an upload that failed appears in errors with its uploadId, code, reason and whether it is retriable, and the others still finish. The stored size is checked against the plan's upload size and the type is read from the file's first bytes; a file over the limit, or one whose bytes are not the type it was uploaded as, is deleted and that upload fails. Each file is added to the media library unless addToMediaLibrary is false. The returned url with mediaType can be passed to create_scheduled_post as the post's media, the same as a result of upload_media_from_url; a PDF (mediaType document) is for a flow message's file block and is refused as post media. Calling it again for the same upload returns the same result.
find_next_slot
ChatGPTLook 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. Read only: nothing is held or changed. To schedule straight into the next free slot, call create_scheduled_post with nextSlot: true instead.
generate_flow
ChatGPTBuilds a complete automation flow (a draft, never published) from a natural-language description. - description: what the flow does, the trigger and the outcome. - businessContext (optional): industry, product, keyword, offer (a link or lead magnet), tone, dataFields. Supply a link either here or in description, not both. - accountId: the connected account, by id or @handle. With one account on the platform it can be omitted. - variants: 1 to 3 drafts to compare. - iterateOnFlowId (id or name): rebuilds a flow this tool built that nobody has edited since. For a single change to an existing flow, update_node, add_node and delete_node are the tools. The build runs in the background, usually 10 to 30 seconds. The result has one artifact per variant with its flowId and a link to open it in SociaHive. A failed build reports artifacts[i].error with reason, message and recovery.kind: ask_user means the message lists what is missing, retry_same means the same request can be sent once more.
generate_flow_v1_0_0
ChatGPT[DEPRECATED — migrate to a non-deprecated version of generate_flow] DEPRECATED — use generate_flow@2.0.0 (inline streaming in chat). Kept for MCP synchronous clients that can't consume two-phase tool resolution. Generates a complete automation flow from a natural-language description; returns a draft + builder URL the user opens to watch the AI assemble the flow.
generate_multiple_flows
ChatGPTBulk-build automations from ONE whole-setup description (migration: "rebuild my ManyChat setup"). Splits into ≤10 automations, each generated as a background DRAFT flow — nothing goes live. ONLY for MULTIPLE automations described at once; a single automation uses generate_flow. Call this DIRECTLY as your first action — no whoami/context lookup needed first.
generate_post_image
ChatGPTMake 1 to 4 AI images for a post from a description (prompt) or from the post caption (caption). Pick aspect for the platforms: square for Instagram and Facebook, portrait for Pinterest and TikTok, landscape for X, LinkedIn and YouTube. Each image is saved to the user's media library and costs 5 AI credits (refunded if it fails). Nothing is posted: to use an image, pass its url with type image to create_scheduled_post. Make one unless the user asks for options.
get_analytics_overview
ChatGPTFetch aggregate analytics across all published posts — total impressions, total engagement, post count, per-platform breakdown, and the last 30 days timeline. Optionally filter by date range (YYYY-MM-DD) or platform. Use when the user asks "how did my content perform last week?" / "what's my engagement on Instagram?".
get_capabilities
ChatGPTList what each connected account can DO — automation (DM/comment triggers) vs scheduler (post scheduling). Use when the user asks "can my Twitter account run automation?" or "what platforms can I schedule on?". Returns a static platform-capabilities map plus the user's per-account list.
get_collected_data
ChatGPTSummarize the data collected by a flow — total count, breakdown by field type, last N submissions (metadata only — actual values are not exposed to the LLM for privacy). Use when the user asks "how many emails has my flow collected?" / "what data did this flow gather?".
get_content_insights
ChatGPTGet this account's content performance insights: which formats, days of week, and content pillars index above/below the account's average engagement (with sample sizes), plus top/bottom posts. Use for 'what's working', 'when should I post', 'what content performs best'. Honest insufficient_data below the statistical floor.
get_flow
ChatGPTFetch one flow by id. Use to SEE / inspect / open a flow — "what does this flow do", "show me the welcome flow", "how is this configured", "what triggers does it have". On a flow page the id is already in <page_context>; call directly with it. NOT a lookup before an edit — if the user asked to CHANGE something (copy, keyword, delay, name, status), call the write tool instead. Returns the steps, connections and what stops it running; pass nodeId (id or name) for one step's data.
get_flow_revisions
ChatGPTList the version history of a flow. Returns the most recent N revisions (default 50, max 200) ordered newest-first. Each row carries the version number, when it was created, who/what created it, and a short summary. Use this when the user asks "show me what I had before" or wants to revert.
get_flow_stats
ChatGPTFetch execution analytics for one flow — total triggers, button clicks, unique users, status breakdown, last 7 days daily timeline. Use when the user asks "how is my welcome DM performing?" / "show stats for this flow" / "is the flow getting any traffic?".
get_latest_published_media
ChatGPTResolve the user's SINGLE most recent item published ON THE PLATFORM — singular intents pointing at the live account ("my latest reel", "our last post on Instagram"), or targeting a published post for a flow trigger. A bare "my most recent post" with no platform cue is scheduler-side: use list_scheduled_posts (sortOrder "desc", limit 1). Returns one MediaItem (no picker, no table). Pipe mediaId straight into downstream tools (e.g. plan_flow.trigger.config.media_ids: [mediaId]) without asking the user to choose. Optional mediaType filter narrows to the most recent reel / post / story / carousel. Throws not_found when the account has no matching media. Use list_published_media instead when the user wants to BROWSE multiple items.
get_pixel_embed
ChatGPTGet the user's SociaHive Pixel install snippet + instructions. Use for 'install the pixel' / 'track events on my site'. Returns create-one-first instructions when no pixel exists.
get_post_analytics
ChatGPTFetch per-platform analytics for one published post — impressions, reach, engagement, likes, comments, shares, saves, clicks. Use when the user asks "how is my post performing?" / "show me stats on this post". Returns one row per platform target. Returns an empty list when the post has no analytics yet (newly published, or platform doesn't expose metrics).
get_post_link_clicks
ChatGPTClicks on the short links of a scheduled or published post. When short links are on, each link in a post is replaced at publish by a https://www.sociahive.com/l/<code> link per account; this returns every such link with its destination, total clicks and clicks per day for the last 30 days (UTC). Link previews and crawlers are not counted. Empty when the post had no links shortened.
get_published_media
ChatGPTFetch a single platform-published media item by its mediaId (the platform's own ID, e.g. Instagram's media id). Platform-published, not scheduler-side. Returns full caption (no truncation). For scheduler-side posts use get_scheduled_post. Returns not_found if the media id doesn't belong to the currently selected account.
get_scheduled_post
ChatGPTFetch one scheduler-side post by id (drafts / queued / recurring / scheduler-published). Scheduler-side, not platform-published. Call AFTER list_scheduled_posts when the user references a specific scheduler entry. For platform-published media use get_published_media. Returns full text + recurrence + status detail, each platform's result (status, the error when it failed, the live link), and the post's comment automation when it has one. Use it to answer why a post failed on a platform.
get_scheduler_calendar
ChatGPTGet scheduler-side posts in a date range. Scheduler-side, not platform-published. Use for "what's scheduled this week?", "show next month's posts", "when is my Tuesday post?". Pass ISO 8601 dates. Capped at 200 posts.
list_account_destinations
ChatGPTDestinations (channels, communities) of one connected account; input checks one the user named. Use the id as target metadata destination_id. Read only.
list_accounts
ChatGPTList the user's connected social media accounts (Instagram, Facebook, etc.). Use ONLY when they ask which accounts they have or whether a platform is connected. NOT a preflight — a platform named inside an action ("post to LinkedIn", "disconnect my instagram") is that action's TARGET; call the action tool. Returns id, platform, username, status and textLimit (most characters a post on the account may have; X is 280 unless the account has an X subscription with long posts on) — never tokens.
list_capabilities
ChatGPTReturns the list of tools available to this user (filtered by tier + flags). Use ONLY when the user asks "what can you do?". NOT a preflight — never call it to check whether a capability exists before acting; the tools you can see are the tools you have, so just call the one that fits.
list_client_invites
ChatGPTList the user's client invite links ("did my client connect their accounts?"): state, how many accounts each added and which ones. Never returns link URLs.
list_evergreen
ChatGPTList the user's evergreen queue (recyclable posts that fill failed Autopilot slots). Use for "what's in my evergreen queue".
list_flows
ChatGPTList the user's automation flows — for BROWSING many. Use when the user asks "what flows do I have?" or wants a recap of active/draft work. NOT a lookup step: for ONE named flow ("show me the welcome flow") use get_flow / search_flows; to CHANGE several at once ("pause all my active flows") use the bulk tool. Returns id, name, status, trigger type, platform, updatedAt, createdAt. For "the oldest flow" pass sortBy: "createdAt", sortOrder: "asc", limit: 1. For "the most recent" pass sortOrder: "desc", limit: 1. Use limit aggressively — never fetch a list and pick in your head. For follow-up pages, pass the previous response's nextCursor back as cursor. Call get_flow for full detail.
list_flows_with_stats
ChatGPTRank flows by a performance metric — triggers, completions, unique_users, or button_clicks. Use for "top N flows by X", "best/worst performing flows", "rank my flows", "flow leaderboard". ALWAYS prefer this over list_flows + multiple get_flow_stats calls — one tool call, server-side join + sort + limit. Default: top 10 published flows by triggers, descending.
list_media
ChatGPTList the images and videos the user uploaded to the scheduler (their media library), newest first. Filter by kind, tag or a search over file names and tags; page with cursor. Use it to reuse a file in a post ("use the photo I uploaded last week"): pass its url with kind as the media type to create_scheduled_post. usedInCount is how many posts use the file. Read only.
list_pinterest_boards
ChatGPTBoards of the user's Pinterest accounts. Pass the chosen id as metadata.boardId on the Pinterest target of create_scheduled_post (not needed with a single board).
list_post_milestone_actions
ChatGPTList a post's milestone actions (called plugs in the app): "when this post gets 100 likes, repost it / add this comment". For a scheduled or published post, with progress (lastValue of threshold) and state, plus which of the post's accounts can carry a plug and the metrics and actions each supports.
list_posting_slots
ChatGPTList the user's posting slots: weekly posting times per account ("every Monday at 09:30, Europe/Berlin, for @shop"). Slots are what "next free slot" schedules into.
list_published_media
ChatGPTList recent media on the user's connected platform (Instagram first), recency-sorted. Browse intent only — use when the user wants to SEE several items ("show my recent reels", "what have I posted this week", "the last few posts"). Returns mediaId / mediaType / caption (truncated 200 chars) / permalink / thumbnail / postedAt, likes, comments (hourly) and 7-day gains. For singular intent ("my latest reel", "the most recent post", "target my last reel for this flow") use get_latest_published_media — it returns one item with no picker render. For a known mediaId, use get_published_media. For caption search, use search_published_media. Platform-published, not scheduler-side (use list_scheduled_posts for drafts/queued).
list_review_links
ChatGPTList the client review links of a post and what the client said ("did my client approve Tuesday's post?"). Shows each link's state, comments, approvals and change requests, and whether the post changed after the last approval. Never returns link URLs.
list_scheduled_posts
ChatGPTList posts from the SociaHive Content Scheduler — drafts, queued, recurring, published-via-scheduler. Scheduler-side, not platform-published. Use for "what's scheduled this week", "show my drafts", "what have I queued", "show me failed publications", and queue-side history ("what posts went out yesterday", "my most recent post"). Call it directly; for one account ("on @handle") pass the handle as accountId. NOT a lookup step: to CHANGE or DELETE posts ("reschedule the launch announcement", "remove all expired drafts") call that write / bulk tool instead. Only when they point at the platform ("on my Instagram", "my latest reel") use list_published_media. Returns id/status/platforms/scheduled_at/preview-text. Superlatives: pass sortOrder ("asc" oldest, "desc" newest) with limit: 1 — never fetch a list and pick in your head. Page by passing the previous nextCursor as cursor. Call get_post for full content.
list_signatures
ChatGPTList the user's saved post signatures (sign-offs appended after a blank line when a post publishes). accountIds is "all" or the connected-account ids a signature applies to; isDefault means it is added to every post on those accounts unless the post picks another one. To pick one for a post pass its id as signatureId to create_scheduled_post or update_scheduled_post, or "none" for no signature. Read only.
list_system_templates
ChatGPTBrowse pre-built system flow templates — common automations like welcome messages, lead generation, and customer support. Use when the user says "what templates are available?" / "show me ready-made flows". Returns names + descriptions; clone via the templates UI or duplicate_flow once selected.
publish
ChatGPTPublish a prepared post (by postId) to its platforms NOW. IRREVERSIBLE — requires confirmation. Records a published-outcome per platform.
publish_flow_changes
ChatGPTPuts the unpublished changes of a live flow live, after the same checks as turning a flow on. Edits to a live flow (add_node, update_node and the other step tools) are saved as unpublished changes while people keep getting the live version. Use this when the person wants those changes to reach people. Two steps: a call with confirm: true and no expectedRev returns the preview (steps added, changed and removed, people partway through a removed step, who made the changes, and rev) without publishing; after the person has seen it and agreed, a call with confirm: true and expectedRev set to that rev publishes. A rev that no longer matches the changes is refused. The flow keeps its status: a paused flow stays paused.
publish_post_now
ChatGPTPublish a post immediately to all configured platforms. IRREVERSIBLE — the agent cannot un-publish. Requires confirmation. "publish this now", "post immediately". Identify it by postName (its caption / opening words) when you have no id.
request_media_upload
ChatGPTStarts 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. Use this when the files have no public URL (they are on the computer the code runs on, or in a Google Drive that is not shared publicly) and the client can run code to send them. Do not use for a file at a public URL: upload_media_from_url copies those in one call. One file is given as fileName, mimeType and sizeBytes; more than one file without a public URL is given as files (up to 25), and the result then has one entry in uploads per accepted file, in the order given, while a refused file appears in errors with its index and reason and the other files still get their URLs. Each file is sent with a PUT of its raw bytes to its own uploadUrl with its own headers (for example curl --upload-file PATH -H "Name: value" URL); a URL and its headers belong to one file. finalize_media_upload with the uploadId of each file returns the URL for create_scheduled_post. Upload URLs expire after 15 minutes. Accepts JPEG, PNG, WebP, MP4 and MOV up to the plan's upload size, given in maxBytes. A PDF is accepted too: it can be sent as a file in a flow message (a WhatsApp document, a Messenger or Telegram file) and is refused as post media.
resolve
ChatGPTAuto-resolve a support conversation (by sessionId) from the knowledge base. Resolves only when confident, else leaves it for a human. Records a resolved-outcome on success.
restore_flow
ChatGPTRestores a deleted flow from the trash as a draft. The flow is identified by flowId or by flowName (its name). Deleted flows stay in the trash for 30 days. The restored flow is off until it is turned on again.
restore_scheduled_post
ChatGPTRestores a deleted scheduler post. The post is identified by postId or by postText (words from its text). A post that was scheduled or waiting for approval comes back as a draft (needsScheduling: true); schedule it again to publish it. An automation that was attached to the post is not restored.
revert_flow_to_version
ChatGPTRevert a flow to a previous version. Forward-only history: this writes a NEW revision whose snapshot equals the target version, then updates the live flow doc to that snapshot. The original revisions stay in history. Use after get_flow_revisions confirms the target version exists.
schedule_post
ChatGPTPut an EXISTING draft on the publishing calendar. "schedule this for Tuesday at 9am", "post this to LinkedIn at 5pm" — the draft is already in hand. FIRST call: name it with postId or postName (its caption / opening words) and give scheduledAt in the user's own words ("tomorrow 9am") or ISO; never look either up first. Supplied CONTENT with no draft ⇒ create_scheduled_post. Moving an ALREADY-scheduled post ⇒ update_scheduled_post. Rejects a post mid-publish. Optional attach_automation (one of template_id, prompt, keyword+link) adds a comment automation, left OFF: user turns it on in the scheduler.
search_flows
ChatGPTDisambiguate a FLOW referred to by name when several could match. Hybrid retrieval; in-flight builds filtered. FLOWS ONLY — never for posts, accounts, links, widgets or anything else; those have their own tools. Not a lookup step: if the user asked to SEE a named flow call get_flow, and if they asked to CHANGE several flows call the bulk tool.
search_published_media
ChatGPTSemantic search across captions of media published on the connected platform (Instagram first). Use for "find posts about our spring sale", "the reel I made about onboarding". Searches captions only — image-content search needs vision embeddings, out of scope for v1. Returns top matches by cosine similarity. Min 3-character query.
summarize_flow_purpose
ChatGPTOne-sentence flow summary. Use ONLY on an explicit summary ask — "summarise", "tldr", "explain the purpose of X", "what is the goal", "short description". A plain "what does this flow do" / "how is this configured" wants real detail: use get_flow. Returns the summary plus its source (client-side sampling or server-side fallback).
update_edge
ChatGPTSends an existing connection of a flow to another step. The flow is named by flowId or flowName. The connection is named by edgeId, or by source and sourceHandle (a handle or label from get_flow's outputs) plus target when that output has several connections. Changes where a button or branch leads. On a live flow (published or paused) the change is saved as an unpublished change: people keep getting the live version until publish_flow_changes puts the changes live.
update_flow
ChatGPTRename a flow or change its description; saved and shown in SociaHive. "rename this flow to X". flowName says WHICH flow (its current name — no id lookup); name is the NEW name. Never changes the steps. Rejects a flow mid-publish.
update_node
ChatGPTChange one existing node — every in-flow content edit. "change the welcome message to X" / "fix the typo" → text; "update the trigger keyword to B" → keywords; "use this link" → link; anything else ("set the delay to 5 minutes") → data, MERGED into the node so nothing else is lost. FIRST call: flowName names the flow and nodeId takes the node's LABEL from what the user said ("the welcome message", "the delay") — the server resolves both, so never get_flow first. Always include the CHANGE in the same call; if the user has not said the new value, ask them first. Rejects published flows.
update_posting_slot
ChatGPTChange a posting slot's accounts, weekday, time or time zone. Only the fields given change. Posts already scheduled keep their times; nothing is published.
update_scheduled_post
ChatGPTEdit a scheduler-side post that ALREADY EXISTS (draft or scheduled) — text, media (replaces all), time, timezone. "reschedule the launch announcement for friday", "move it to Monday". RESCHEDULE always means this tool, never schedule_post. FIRST call: name it with postName ("the launch announcement" — its caption / opening words) and the time in the user's own words ("friday", "monday 9am"); never list posts first. Scheduler-side, not platform-published. Rejects published / publishing.
upload_media_from_url
ChatGPTCopy an image or video into the user's SociaHive uploads and return a URL on our storage. Pass url for a file on the web, or, in ChatGPT, file for one in this conversation: an image you generated or one the user uploaded. Use before create_scheduled_post: pass the returned url with mediaType as the post's media. Accepts JPEG, PNG, WebP, MP4 and MOV up to the plan's upload size. Never publishes anything.
whoami
ChatGPTReturns the calling user's identity, tier, surface, and currently selected connected account. Use ONLY when the user asks who they are, what plan they are on, or which account is selected. NOT a preflight — never call it to check the account or tier before a write; your instructions already carry the account scope and the server enforces tier regardless.