# Create and publish social posts Source: https://docs.native.no/mcp/social-posts > **Live connector.** Sign in with your Native account. Available tools depend on account access, workspace features and server write settings. Newsletter MCP tools in this release await public deployment; their guides state the requirements. Blog copy preparation does not include CMS publishing. Turn a brief into Native social drafts, review copy and media, then schedule or publish to connected channels. ## Give the assistant a useful brief Name the brand, audience, topic, language and destinations. Supply facts such as dates, prices and booking links. Say whether you want ideas, saved drafts or publishing. Ask for existing library pictures when you want to preserve a product’s appearance. A week of drafts: ```text For Harbour Bakery, create three Norwegian Instagram and Facebook drafts for next week: our sourdough class, our weekday breakfast and a behind-the-scenes story. Use our Native voice and library photos. Ask me for missing facts. Leave everything as drafts. ``` ## Read the brand and its channels The assistant resolves the workspace and brand, reads `get_brand_voice`, checks `get_profile` and uses `get_calendar` to avoid clashes. It must ask you to choose when discovery returns `needsUserChoice: true`. A channel that needs reconnection can still have useful historical data; it is not ready to publish. ## Create one post or a batch | Task | Tools | What to check | | --- | --- | --- | | One draft | `create_draft` | Read the returned post and its media state. | | Several drafts from one brief | `create_posts`, then `get_post_batch_status` | Keep the batch id. Inspect each item, failures and pending images. | | Read a saved post | `view_post` | Use this result for copy, pictures, destinations and review state. | | Compare a set of posts | `view_posts` | Use returned ids rather than recreating drafts. | For a batch, wait for `settled: true` and check `imagesPendingCount` when present. Settled copy can include failed or skipped items, and pictures may still be rendering. Report the drafts that succeeded and the ones that did not. ## Edit the draft | Change | Tools | | --- | --- | | Caption, first comment or destination copy | `update_post` or `generate_caption` | | Add or remove destinations | `add_post_platforms`, `remove_post_platforms` | | Use a brand library picture | `attach_image_to_post` or `replace_post_image` | | Generate or revise a picture | `generate_image` or `regenerate_post_image`, then `get_generation_job` when a job id is returned | | Adjust carousel slides | `remove_post_image`, `reorder_post_images` | | Use a library video | `attach_video_to_post` | Read the post again after an edit. Changing copy or pictures on a scheduled post can affect content already booked to publish; the assistant should make only the change you requested. Exact tool arguments come from the current connection’s schema. ## Review the exact version Inspect each destination’s wording, pictures and state. If Native requires recorded approval, `approve_post` takes the post’s `id` and the `expectedDigest` from the version you reviewed. If the version changes, read it and collect a new decision. `reject_post` records a reason for changes. `share_post_for_review` can create a review link. It sends review emails only when recipients are supplied, so name recipients only when you want those emails sent. `get_post_feedback` reads their responses. Feedback alone does not replace the recorded decision used for publishing. ## Schedule or publish 1. Name the reviewed post, social destinations and publishing time. Include a timezone, such as `Europe/Oslo`, so the assistant can send an ISO 8601 timestamp with an offset. 2. Use `schedule_post` for one post or `reschedule_posts` for a bounded set. `publish_post_now` publishes immediately within your request. 3. Read `get_post_status`. Report `platformResults` per destination and include `publishedUrls` where present. 4. If one destination fails, inspect its error and retry only the failed destinations that your request covers. Do not re-publish destinations already live. A timestamp on a draft is not proof that it has been scheduled. A successful tool response is not proof that every destination published. Use the returned state and final URLs. ## Change plans Use `move_platform_to_drafts` to make one destination an undated draft, or `unschedule_platform` to withdraw the specified destination’s booking. They address a `platformPostId`. `unpublish_post` takes published content down where supported; `delete_post` removes an unpublished Native post. Each is a separate change that needs to fit your request.