Posty

This tool allows you to schedule a post to a social media platform, based on get_integration_schema tool. So for example: If the user want to post a post to LinkedIn with one comment - socialPost array length will be one - postsAndComments array length will be two (one for the post, one for the comment) If the user want to post 20 posts for facebook each in individual days without comments - socialPost array length will be 20 - postsAndComments array length will be one Call preview_post with the same payload first and show the user what it returns — account name and @handle, the local publish time, the character counts — and only call this once they have confirmed. preview_post writes nothing. If a tool returns an error, correct the parameters and try again. RETRYING: pass an idempotencyKey (a UUID you invent) on every call. Then, if the call times out or you are unsure whether it went through, resend the SAME request with the SAME key — you get the original result back and nothing is created twice. WITHOUT a key this tool is not idempotent and a blind retry can post the same thing twice in public; use list_posts to check before retrying in that case. To undo a post created here, use delete_post with the postId this returns — but only before it publishes.

create_post

Get a browser link the user can drop files on, for a file that is on THEIR device and that you cannot fetch by URL. Use this when the user wants to post an image or video they have on their phone or computer. Do not ask them to host it somewhere public first. The flow, in order: 1. Call this tool. Show the user the returned url and say: "Open this link, drop the image or video there, then come back and tell me it is done." 2. When the user says the upload is done, call list_upload_link_files with the uploadLinkId from this call. It returns the files with their hosted path. 3. Pass that path as the create_post attachment. The link is valid for 120 minutes and takes several files. It works signed out, so the user can open it on their phone. Call this once per batch; if it expires, call it again for a fresh one.

create_upload_link

Delete a post from the user's Posty calendar — the undo for create_post. Take the postId from list_posts or from create_post's own result. REFUSES A POST THAT HAS ALREADY BEEN PUBLISHED. Posty cannot remove a post from the platform; deleting the Posty record would leave it live with nothing pointing at it. Check "state" in list_posts first — only QUEUE, DRAFT and ERROR posts can be deleted. A post that went to several channels at once is deleted from ALL of them: they are one post in Posty. The result names every channel it removed, with the @handle, so you can tell the user exactly what is gone. If any channel of that group has already published, nothing is deleted at all. Ask the user before calling this. It cannot be undone.

delete_post

Look up channel-specific options that a post needs but the user cannot be expected to know — a subreddit, a Pinterest board, a Discord or Slack channel. Many channels have none. Call get_integration_schema first to find the available methodName values for the channel; if it returns none, this tool has nothing to look up. methodName is required. [input:callable-tools]

get_channel_options

Everytime we want to schedule a social media post, we need to understand the schema of the channel we are posting to. This tool helps us get the schema, the rules and the real character limit of one connected channel. Pass the integrationId from list_integrations — NOT a platform name — because the limit depends on the account, not only on the platform (an X account with Premium/Verified may post far more than one without). Sometimes we might get a schema back that requires some id, for that, you can get information from 'tools' And use the get_channel_options tool to fetch it.

get_integration_schema

Get the current time and the user's timezone before you compute any post date. Call this FIRST in any conversation that mentions a time — "tomorrow at 9", "next Tuesday", "in two hours". Posty stores post dates in UTC, and create_post refuses a scheduled date in the past, so a wrong timezone assumption is a failed call at best. Returns the server's current UTC instant, the user's IANA timezone as they set it in Posty, and the matching local time. If "timezone" comes back null the user has never set one — ask them for it rather than assuming, and say the timezone back to them whenever you quote a time.

get_workspace_context

This tool lists the available groups (customers). Use a group id with the list_integrations tool to filter the integrations belonging to that group

list_groups

This tool list available integrations to schedule posts to. Optionally pass a group id (from the list_groups tool) to only list integrations belonging to that group

list_integrations

List the posts already in the user's Posty calendar — scheduled, drafted, published or failed — so you can answer "what is going out on Friday?" and find a post the user wants changed or cancelled. Writes nothing. Returns, per post: the postId (pass it to delete_post), the state, the publish time in BOTH UTC and the user's own local timezone, the channel's name and @handle and platform, and a short plain-text preview of the content. The channel fields are spelled exactly as create_post spells them in its result, so a post you created earlier in this conversation can be matched to a row here. Defaults to the next 30 days. Pass fromUtc/toUtc for any other window — call get_workspace_context first if the user gave you a local date, because these are UTC.

list_posts

The files the user dropped on an upload link from create_upload_link, with the hosted path to attach to a post. Call this after the user tells you the upload is done, with the uploadLinkId you were given. Pass each file's PATH - not its id - as the create_post attachment. If status is "empty", nothing has arrived yet: tell the user you do not see the file, ask them to check the page showed "uploaded", and call again when they confirm. Do not search the media library instead, and do not ask the user for a path.

list_upload_link_files