Bolta Platform Tailoring

Bolta — Platform Tailoring

Add the platform-specific extras a post needs: a poll, a subreddit flair and title, a video privacy setting, a Pinterest board, a YouTube title. Threads polls have a dedicated poll param on create-post; everything else — including X polls — goes through the platform-details tools.

When to use

The user wants fields that are specific to one platform — not just text (bolta-draft-post) or media (bolta-post-media).

Tools this skill uses

Prerequisites

• workspace_id — resolve once via list-workspaces, reuse. Auth is automatic via the Bolta connector's OAuth grant — never ask for an API key. Default new content to Draft; confirm before publish/delete.
• The post_id for an existing post (or create one first).
• One post → create-post. Two or more → bulk-create-posts. Adapting an idea for several platforms is the two-or-more case, so it starts with one bulk-create-posts call and not a loop: looping create-post renders a separate card per post and the user only ever sees one of them. Apply per-platform fields afterwards, per post. (This skill is about the per-platform details; it is not a reason to create posts one at a time.)
• The exact platform slug: one of x, threads, linkedin, facebook, instagram, bluesky, mastodon, discord, reddit, tiktok, pinterest, youtube, wordpress.

Critical: unknown keys are silently dropped

The server ignores any fields key it doesn't recognize and still returns success. A typo (privacy instead of privacy_level) is a reported-success no-op — nothing saved, no error. So after every update-post-platform-details, ALWAYS do a verify-read: call get-post-platform-details(post_id, platform) and confirm each value you set actually came back changed. If a value didn't stick, the key name was wrong — use the table below.

Workflow

Polls

• Threads: pass a poll object to create-post: poll = { "options": ["Ship it", "Wait"], "duration_minutes": 1440 }.
• X: the create-post poll param does NOT work for X — the X publisher only reads XPostDetails.poll_options, and nothing syncs the two. An X poll set via create-post publishes as a plain tweet with no poll and no error. Route X polls through update-post-platform-details(post_id, "x", fields={"post_type": "POLL", "poll_options": ["Yes", "No"], "poll_duration_minutes": 60}). post_type must be "POLL" or the options are ignored at publish time.
• Mastodon: poll_options (list) + poll_expires_in (seconds, not minutes) via update-post-platform-details.

Richer per-platform fields

1. Resolve post_id (create the post first if needed).
2. Read current values: get-post-platform-details(post_id, platform).
3. Set values: update-post-platform-details(post_id, platform, fields={...}). fields is an object of platform-specific keys — set only what you're changing. Use the exact key names below; anything else is silently dropped.
4. Verify-read: get-post-platform-details again and compare against what you sent.
5. Confirm back what was set. Keep new content as a Draft unless the user asked to publish.

Field names by platform (verified against the server)

Note the naming traps: Reddit flair is flair_id/flair_text (not flair), TikTok is privacy_level with the enum values above (not privacy: "public"), YouTube is video_title/privacy_status (not title/privacy), Pinterest takes a board_id FK (not a board name). When in doubt, call get-post-platform-details first and mirror the key names it returns — don't invent field names.

Failure handling

• Unknown platform slug → confirm the exact platform; only the 13 listed above are valid.
• Verify-read shows a value didn't stick → the key was silently dropped; fix the key name from the table above and resend.
• Required-relation 400 (Reddit selected_subreddit_id, Facebook primary_page_id) → the first-time save needs that ID; look it up before creating details.
• Poll with fewer than 2 options or an invalid duration → fix before sending.
• Setting details on a post not connected to that platform → the post's account_ids must include an account for that platform; add it via bolta-draft-post/update first.
• Permission error → report the missing role/scope; leave the post as-is.

Example

User: "Set the Reddit post's flair to Discussion and give it a title."

1. list-workspaces → workspace_id; resolve post_id.
2. get-post-platform-details(post_id, "reddit") → current values; note whether selected_subreddit_id is already set (required on first-time creation).
3. update-post-platform-details(post_id, "reddit", fields={"flair_text":"Discussion","title":"How we cut build times 40%"}).
4. get-post-platform-details(post_id, "reddit") → confirm flair_text and title stuck.
5. "Reddit flair set to Discussion with that title. It's still a Draft — schedule or publish?"