publish_post
Returns a link the user opens to publish a draft themselves. Publishing is irreversible, and it goes out under the user's own name, so over MCP this tool does NOT publish: it returns a link the user opens to see the copy and the channels and press Publish themselves. Show them the link and wait. Do not try to confirm on their behalf. There is no argument that does that, and any you invent is ignored. (Over SMS/WhatsApp, where the user types publish 123 themselves, it publishes directly.) When the account has multiple connected accounts for a platform, pass platform_account_ids to target a specific one; the confirmation page names the account it will publish to.
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": {
"id": "<id>"
},
"name": "publish_post"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Post id | |
| platforms | No | Optional. Defaults to the channels already selected on the draft. Instagram needs an image or video on the post: if it has none, add one with `update_draft` (`images`) first. | |
| workspace | No | Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that. | |
| platform_account_ids | No | Optional map of platform => connected_account_id (numeric id from `list_connected_accounts`). Example: {"linkedin": 42} to publish to the LinkedIn account with id 42. Each id must belong to the current account and match the platform. |