# Create Meta ads Source: https://docs.native.no/mcp/ads > **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. Generate Meta ad drafts, refine their images and copy, then review publishing setup and spend before going live. > **Availability follows your connection.** Ads require workspace access to Native ads. The server may expose creative tools without publishing tools, or hide ads entirely. Check the authenticated tool list before promising an action. A generated ad is a draft and starts no spend. ## Start with the creative brief ```text For Harbour Bakery, create one Meta ad draft promoting our Saturday sourdough class. Use our selected class product and an existing library photo without changing it. The confirmed price is NOK 650. Keep it as a draft for review. ``` Generation needs no connected Meta account, campaign, budget or targeting setup. Those are publishing decisions. Begin with the selected brand, its voice and any relevant products or brand assets. ## Generate a creative or a pack | Task | Tools | Readiness | | --- | --- | --- | | One creative | `create_ad`, then `get_ad_status` | Keep `creativeId`. Wait for `ready` or report `failed`. | | A pack of 5 to 50 creatives | `generate_ad_batch`, then `get_ad_pack_status` | Keep the returned pack id. Inspect completed and failed slots. | | Read existing drafts | `list_ads`, `get_ad_status` | Use the saved creative instead of generating a duplicate. | | Preview a selected creative | `get_ad_preview` | Check the copy, image, state and Native app link. | Ad generation can take minutes. For one-off creatives, create one at a time and follow its progress. Use a batch for a pack of alternatives. After an uncertain write outcome, inspect the saved state before creating another. ## Choose how Native uses images | Input | Meaning | | --- | --- | | `imageIds` | Place brand library images as they are and skip new artwork generation. | | `productIds` | Select products that the creative is about. Read the catalog first. | | `assetIds` | Select brand-DNA assets, such as a team member, review or customer story. These are not library image ids. | | `referenceImageUrls` and `imageBrief` | Guide a new image render. A reference is not a promise to place the existing picture unchanged. | | `from` | Start from an existing post or ad using the source type and id accepted by the tool. | Use `search_brand_library`, `list_products` and `list_brand_assets` to obtain the right ids. `imageIds` cannot be combined with `imageBrief` or `referenceImageUrls`. If a named product is missing, ask what to use instead of silently substituting another product. ## Refine and review - Use `update_ad_draft` for copy and click-through URL changes. `create_ad` does not take a destination URL. - Use `regenerate_ad_image` for a new render, or `add_ad_image` to place a library image. Use `remove_ad_image`, `revert_ad_image` and `create_ad_renditions` only for the requested changes. - Read the creative again and show the exact version for review. Where available, `approve_ad` records approval of its current digest; `reject_ad` records the reason for changes. - On a connection without `publish_ad`, hand the chosen draft to the user in Native using the returned app link. ## Choose the publishing destination When publishing is requested and supported, read `get_ads_overview`. Check the connected Meta account, actual destination URL and campaign/ad-set choices. A null destination URL needs a user-provided URL; `update_ads_setup` sets the brand default. An ad draft can have its URL updated separately. For a first campaign, offer Native’s setup wizard via `setup.appUrl` or setup in the conversation. Use the user’s chosen route. If they want to use an existing Meta ad set, inspect that path rather than creating a new Native campaign automatically. For new campaigns, the user chooses the goal, location, daily budget and budget level. Conversion goals need an appropriate pixel and event. Use `search_geo`, `estimate_reach`, `list_meta_pixels` and `get_meta_pixel_activity` as needed. Do not infer a spend decision from the creative brief. ## Publish within the approved scope `publish_ad` publishes a chosen creative into the selected destination when available. Publishing or activation can start real spend. Confirm the creative, account, ad set, destination URL and applicable budget before that action. A pack is not published wholesale: each selected creative has its own publish call. Read the result and subsequent ads state. Use `get_meta_ad_preview` for Meta’s render of an ad already on Meta; a generic draft preview is not proof that the ad is live. Distinguish draft, approved, deployed, paused and delivering states. ## Manage delivery and performance When exposed, `pause_ad`, `pause_ad_set` and `pause_campaign` stop the corresponding delivery. Their activate counterparts resume it. `update_campaign_budget` changes spending on a live campaign. Changes to ads autopilot can authorize recurring activity, so handle them as separate requests with their own settings and scope. Use the [Analytics guide](https://docs.native.no/mcp/analytics) to compare results. Generating, approving and publishing are distinct steps; none should be reported as another.