create_post
Post, publish or schedule a social media post: a post on a Facebook page or LinkedIn, an Instagram post or Reel, a tweet or thread on X (Twitter), a TikTok or YouTube Short, a Pinterest pin, or a post on Threads, Bluesky, Telegram, Discord or Slack. You (the AI) write it; Postemi publishes it automatically now, at the scheduled time, or on many days, or saves it as a draft. Use it after the user confirmed the preview_post result.
Follow the rules get_integration_schema returned for each channel. One socialPost entry per channel and time; postsAndComments holds the post, then its thread parts (X, Threads, Bluesky) or comments (LinkedIn, Facebook). A LinkedIn post with one comment is one socialPost with two postsAndComments; 20 Facebook posts on 20 days are 20 socialPost entries with one each.
Call preview_post with the same payload first, show the user the account, @handle, local time and character counts, and call this only after they confirm. If a call returns an error, fix the parameters and try again.
Always pass an idempotencyKey (a UUID you invent). If a call times out or you are unsure it went through, resend the SAME request with the SAME key: you get the first result back and nothing posts twice. Without a key a blind retry can post twice in public; check list_posts first.
To undo, call delete_post with the returned postId, before it publishes.
Magyarul: poszt kitétele, posztolás, ütemezés, időzítés, közzététel, megosztás.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"socialPost": "<socialPost>"
},
"name": "create_post"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| socialPost | Yes | Individual post | |
| idempotencyKey | No | Optional. A unique id you invent for THIS post (a UUID is ideal). If the call times out or errors and you are not sure whether it went through, send the SAME request again with the SAME key: you will get the original result back instead of a second post. Honoured for 24 hours. Use a NEW key for a genuinely new post — reusing a key with different content is refused. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| errors | No | ||
| output | No | ||
| notices | No | Things the user must be told about what was saved, e.g. links removed from an X post (X does not get links). Relay them. | |
| replayed | No | True when this result is a replay of an earlier call with the same idempotencyKey. Nothing new was created. |