prune_media_reference exists to fix a specific failure — a dangling media reference blocking a post from sending — and nobody builds that tool before they have watched it happen. Same with the idempotency key on create_post: it means someone lost a retry into a duplicate tweet. Combined with the LinkedIn engagement surface, this reads as a product used daily rather than shipped and forgotten.
Publora's hosted endpoint for social scheduling. Their own guidance is worth repeating: for a fully autonomous agent they recommend the REST API, and reserve the endpoint for interactive assistants.
- Posting — create_post, update_post, delete_post, get_post, list_posts with filters by status, platform and date
- Media — get_upload_url for local files, complete_media to finalise, delete_media and prune_media_reference to repair a stuck post
- Accounts — list_connections across Twitter, LinkedIn, TikTok and the rest
- LinkedIn specifically — reactions, comments, reshares, and listing people captured from engagement on your company page
A bearer API key. Media can be passed as public https URLs, which the docs call the fastest route — Publora downloads them itself rather than making you upload.
Paste a URL with a key — add the endpoint to your client