1Social

Checks a draft post against each selected network WITHOUT publishing it, and reports what would go wrong: per-segment character counts against each limit, whether a network requires an image, whether a multi-segment post will publish as a native thread or be joined into one post, and what the post would cost against the remaining quota. Pass any attached image or video in `media` (or `mediaUrls` if you only have a public link) so the check accounts for it. Always call this before publish_post — it is free and it is the only preview that exists.

preview_post

Records the answer to a delivery 1Social could not determine: whether the post is actually live on that network. The USER must check the network and say — never infer this, and never call it on their behalf without an explicit answer. Confirming that a post is live commits the quota it used; confirming that it is not marks the delivery failed so it can be retried.

confirm_delivery

Deletes a post from 1Social and attempts to remove the published post from each network. Removal works on X, LinkedIn, Bluesky and Facebook; Instagram, TikTok and Threads expose no working delete API, so a post that went to them STAYS LIVE and only the user can take it down. On a thread, only the first post is removed and the remainder stay live as orphans. The result reports what actually came down, per network — report that to the user accurately rather than confirming a clean delete. Confirm with the user before calling this.

delete_post

Changes the content and scheduled time of a post that has not been sent yet. Only works while the post is still editable — a post that is published, in progress, or cancelled cannot be edited. The networks have no edit endpoint, so this withdraws the scheduled post and replaces it; if some networks accept the replacement and others do not, the result names the ones that kept the old version.

update_post

Lists the social accounts the user has connected to 1Social, what each network will accept (caption length, whether media is required, whether it can thread), the current plan, and the remaining monthly posting quota. Call this before composing anything: channel ids from here are required by every other tool. Connecting a new account needs a browser and cannot be done from a chat.

list_accounts

Lists the user's posts with the outcome on each network: delivered, failed with a readable reason, cancelled, or `unknown` when 1Social genuinely cannot tell. Includes stored engagement metrics where the network reports any. Pass postId to fetch one post, status to filter, or limit to shorten the list. Delivery ids needed by retry_delivery and confirm_delivery come from here.

list_posts

Publishes a post to the user's connected social accounts, or schedules it for a future time by setting scheduledAt (null publishes immediately; the limit is 30 days ahead). Run preview_post first and resolve any issues — this tool refuses a post that exceeds a network's limits. To attach an image or video the user shared, pass it in `media` (or `mediaUrls` if you only have a public link); Instagram and TikTok reject a post that has none. Pass a stable idempotencyKey so a repeated call cannot publish the same thing twice. The result is a per-network receipt: some networks can succeed while others fail, and that outcome must be reported to the user network by network.

publish_post

Retries one failed delivery to a single network, leaving the deliveries that already succeeded untouched. Retrying spends quota again. It is refused for a permanent failure such as a revoked credential or a policy rejection, because it would only fail again. For a delivery in the `unknown` state, `force` is required and retrying MAY publish a second copy — ask the user before doing that.

retry_delivery

Cancels a scheduled post so it will not be published, and releases the quota it had reserved. The post stays in the list with a cancelled status and its receipt intact. Use this rather than delete_post when the post has not gone out yet.

cancel_post

Gets an upload target for a file you hold locally, for clients that cannot attach files to a tool call. Use it ONLY when you have the file itself and no public link — if the user attached something, pass that in publish_post's `media` instead, and if you already have a public https link use `mediaUrls`. The flow is: 1. Call this tool with the file's name, MIME type and size. 2. PUT the raw bytes to the uploadUrl it returns, sending uploadHeaders exactly as given. 3. Pass the returned publicUrl in `mediaUrls` when you call preview_post or publish_post. The upload target is short-lived, so do step 2 straight away. Serving the file from a local web server instead does not work: only public https links are accepted.

upload_media