MCP & Automation

Launch Facebook Ads with AI: Meta and TikTok from Claude

How to launch Facebook and TikTok ads with AI from Claude: the inputs to prepare, the dry-run to live flow, what Whathead checks before spend, and prompts to copy.

Cover: Dry run first, then go live. A dry-run payload, campaigns created paused on Meta and TikTok, then you confirm going live.

Most launch mistakes I see aren’t strategy mistakes. They are a wrong pixel event, a budget at ad set level when the plan said campaign level, a UTM with last month’s campaign name, or a campaign that went live before anyone looked at it. An AI assistant doesn’t remove those risks; it can repeat them faster. The workflow around it is what lowers the risk: inputs Claude can read, previews you check, and a paused state between “built” and “spending”. This guide is that workflow for Meta and TikTok, run from Claude through the Whathead MCP server. For the general QA list, use our paid media launch checklist; this post covers the parts that change when an AI builds the campaign.

Can an AI ad manager launch campaigns on its own?

Technically, yes. Through an MCP server with write access, Claude can create campaigns, ad sets, creatives and ads on Meta and TikTok, upload media and set budgets. Whether it should act alone is a different question, and the answer is no.

An AI ad manager is good at the mechanical part: turning a plan into correctly shaped API calls, repeating the same structure across markets, and noticing a missing field. It is bad at what isn’t written down: that the client asked to drop a region last week, or that the landing page goes live tomorrow, not today. So split the job. Claude builds and checks; a person approves and activates.

One naming note: on Meta, “AI” often means Meta’s own automation. Advantage+ campaign budget, audience and placements are levers Claude sets through the API like any other field, and Meta only labels a campaign Advantage+ sales, app or leads when all three are on (Meta docs). Decide them in the plan, not in the chat.

What should you prepare before asking Claude to launch?

Claude builds from what is written down. Anything missing from the inputs becomes a guess, and guesses are where launches go wrong.

Inputs

What Claude needs before a launch

 What to provideWhy it matters
Media planObjective, markets, budget type and amount, flight dates, audiences and KPI per lineThe plan is the spec; Claude should not fill gaps on its own
Naming conventionThe pattern plus one worked example per levelNames drive reporting and UTMs
TrackingPixel or dataset ID, the optimization event, the UTM templateA wrong event or pixel is the most expensive silent mistake
CreativesFinal files or library IDs, copy, CTA and URL per adClaude can upload, but can’t tell whether a file is the approved version
Account accessAd account ID, Facebook Page or TikTok identity, Business Center roleWrites fail, or land in the wrong account
Special rulesSpecial ad categories, exclusions, brand safety requirementsMeta requires special ad categories to be declared on the campaign

Paste the plan into the chat or attach the spreadsheet, then ask Claude to restate it as a table before it builds anything. If the restated plan is wrong, the build will be wrong. Related guides: from media plan spreadsheet to live campaigns, ad naming conventions and tracking QA.

How does the dry-run to live flow work?

Dry run to live

Six steps from plan to spend

  1. 01ReadClaude lists accounts, pixels, Pages, identities and existing campaigns
  2. 02Build as dry runEach create returns the exact API request; nothing is sent
  3. 03ReviewYou check objective, event, budget, targeting, status and names
  4. 04Create pausedThe same calls run live with dry_run false and a paused status
  5. 05QAPreviews, tracking and ad review in Ads Manager
  6. 06ActivateA separate status change you ask for and confirm
  • Dry run by default. In Whathead, Meta and TikTok write actions run as a dry run unless the call sets dry_run to false. The dry run returns the request Whathead would send (method, path and payload) plus any warnings, and nothing reaches Meta or TikTok.
  • Two kinds of approval. Claude asks you to approve each tool call unless you have chosen “Allow always” (don’t, for write tools). Whathead adds its own rule: destructive actions such as deletes are refused live unless the call also includes confirmed: true.
  • Paused is your job. On the native Meta and TikTok gateways, Whathead sends the status you ask for; it doesn’t force one. Meta accepts only ACTIVE or PAUSED when you create a campaign or ad set, and TikTok’s campaign create defaults operation_status to ENABLE (TikTok API docs). Put PAUSED and DISABLE in the prompt and check them in every preview. TikTok asks you not to pass DISABLE for Reach & Frequency campaigns, so treat those separately.
  • Activation is a separate step. Going live is a status change you request after QA, previewed and confirmed like any other write.

What does Whathead check before anything spends?

Checked on 19 Nov 2026

Checks on Meta and TikTok writes

 MetaTikTok
Writes default to a dry runYesYes
Ad account must be connected to your workspaceChecked on every call, dry runs includedAdvertiser access checked on every call
Connection must allow writesThe read-only address and read-only tokens can’t writeSame
Destructive actions need confirmed: trueYesYes
Role check before campaign createYour Meta permissions apply at MetaBusiness Center role (Admin or Operator) verified; create is refused if it can’t be confirmed
Status on createWhatever you send: ask for PAUSEDWhatever you send; TikTok’s default is ENABLE: ask for DISABLE

What Whathead does not check: whether the offer, creative or landing page is right, whether the plan itself is right, or whether the platforms will approve the ads. Meta says its ad review is typically completed within 24 hours and that ads may be reviewed again after they are live (Meta Transparency Center). TikTok says most ads are reviewed within 24 hours, and that editing an ad group’s targeting location or an ad’s creative triggers a new review (TikTok help).

How do you launch a Meta campaign from Claude?

  1. Read the account. Ask Claude to list the ad account’s pixels, custom conversions, Facebook Pages and Instagram accounts, and to confirm which ones the plan uses. Use IDs from here on, not names.
  2. Campaign. Objective (for example OUTCOME_SALES or OUTCOME_LEADS), budget level and status PAUSED. Declare special ad categories where they apply: HOUSING, EMPLOYMENT, FINANCIAL_PRODUCTS_SERVICES or ISSUES_ELECTIONS_POLITICS, and when you select one Meta also requires special_ad_category_country (Meta docs). Budget goes at campaign level or ad set level, not both.
  3. Ad sets. Optimization goal, promoted_object (pixel and event), targeting, schedule, bid strategy and attribution setting, each from the plan. Decide the Advantage+ levers here.
  4. Creatives. Upload images or videos, then build each creative with the Page, copy, CTA and a URL whose UTMs match the names. Generate previews before you create ads.
  5. Ads. Create each ad PAUSED under its ad set with its creative.
  6. Read back. Have Claude read every created entity and compare it with the plan table. Fix mismatches as dry runs before QA.

More on what Claude can read and change on Meta: Meta Ads MCP. For setup, see Connect Claude to Meta Ads.

How do you launch a TikTok ads campaign from Claude?

  1. Check access first. Ask Claude to confirm your Business Center role on the advertiser. Before a campaign create, Whathead verifies an Admin or Operator role and refuses the create if it can’t confirm one, so you find out before the build rather than after.
  2. Pick regular or Smart+. TikTok’s upgraded Smart+ experience covers Traffic, Sales, Lead Generation and App Promotion and puts manual and automated setup in one flow; TikTok notes it may not be available in every account yet (TikTok help). In Whathead, Smart+ campaigns use their own Smart+ actions end to end, because the regular create actions can’t build Smart+ entities.
  3. Campaign and ad groups. Create the campaign with operation_status DISABLE. For each ad group set placements, the optimization event and pixel, budget, schedule and attribution: click 1, 7, 14 or 28 days and view off, 1 or 7 days (TikTok help).
  4. Creative. Upload videos by file or URL and pick the identity. For Spark Ads, authorize the creator’s post with the code they share before you build the ad.
  5. Ads and review. Create ads disabled, preview them, and leave time for TikTok’s review. Finish creative edits before you submit, since editing creative triggers a new review.

If the campaign already runs on Meta, Whathead can copy it from Meta to TikTok as a paused draft, and you review the mapped fields instead of rebuilding. Details on the TikTok side: TikTok Ads MCP.

Why launch paused, and what should you QA before going live?

Paused is the only state where everything exists and nothing spends. It lets you check the real objects in Ads Manager, not a description of them. These are the checks that matter most when an assistant did the build:

Before activation

AI-built campaign QA

  • Every line in the plan exists, and nothing extra was created (ask Claude to count both).
  • Names follow the convention and UTMs match the names.
  • Each ad set or ad group optimizes for the approved event on the approved pixel.
  • Budgets sit at the planned level, with the right daily or lifetime type and amount.
  • Start and end dates are correct in the account time zone.
  • Previews look right in the main placements.
  • Special ad categories are declared where they apply.
  • Ads are submitted for review early enough for the start date.

Creative specs, post reuse and approvals are covered in the paid media launch checklist, and event checks in tracking QA.

What mistakes does an AI media buyer make at launch?

  • Filling gaps with defaults. If the plan doesn’t name an optimization event or audience, the model may pick one. Tell it to stop and ask when an input is missing.
  • Creating live by accident. A create call without a status. On TikTok that means enabled.
  • Wrong account or pixel. Client accounts with similar names. Whathead refuses accounts that aren’t connected, but two connected accounts can still look alike, so give IDs.
  • Budget units and level. Check in the preview that the amount and currency match the plan, and that the budget sits at campaign or ad set level as planned.
  • Duplicates after a retry. If a build fails halfway, rerunning it can create a second copy of what already succeeded. Ask Claude to read what exists before it retries.
  • Editing after approval. Changing creative after review sends the ad back into review on TikTok and can on Meta.
  • “Allow always” on write tools. It removes the one prompt that shows you each change before it runs.

Prompts you can copy

Plan and dry run

  • “Here is the media plan [paste or attach]. Restate it as a table: campaign, ad set or ad group, market, objective, optimization event, budget type and amount, dates, audience and creatives. Don’t build anything yet. List anything missing.”
  • “Using the Whathead Meta tools, build this plan in act_XXXX as a dry run only. Status PAUSED on every entity, special_ad_categories empty, pixel XXXX with the Purchase event. Show each preview and stop.”
  • “Check my Business Center role on TikTok advertiser XXXX. Then build the TikTok campaign from the plan as a dry run with operation_status DISABLE and one ad group per market. Show the previews.”

Create paused and QA

  • “Create the reviewed entities live, paused. After each call, read the entity back and confirm its status before the next one.”
  • “Generate previews for each Meta ad in feed, Stories and Reels formats.”
  • “Read back everything created today in both accounts and compare it with the plan table. List mismatches only.”
  • “Copy Meta campaign Winter Sale to TikTok as a paused draft and list every field I need to fill in.”

Go live

  • “Prepare the status change to ACTIVE for campaign XXXX as a dry run. I’ll confirm before you send it live.”

Launching ads with AI: common questions

Can Claude create Facebook ads?

Yes, through a write-capable MCP server such as Whathead. Claude can create campaigns, ad sets, creatives and ads in Meta Ads. In Whathead each write is a dry run first, and nothing is sent to Meta until a call explicitly goes live.

Will anything go live without my approval?

Not through a dry run, and Claude asks before each tool call unless you allow it permanently. But a live create with status ACTIVE on Meta, or with no status on TikTok, will deliver after ad review, so always ask for paused entities and check the status in the preview.

Can I launch a TikTok Smart+ campaign from Claude?

Yes. Whathead has dedicated Smart+ campaign, ad group and ad actions for TikTok’s upgraded Smart+ experience. TikTok notes the upgraded experience may not be available in every account yet.

Does an AI media buyer replace a human media buyer?

No. It speeds up the build and the checks, and it is good at repeating a structure without typos. Decisions about budget, audience, offer and timing stay with the person who owns the plan.

What do I need to start?

A Whathead plan with MCP access (from $39 a month, with a 14-day trial), Meta or TikTok connected with a role that can create campaigns, and Claude with custom connectors. The same server works in ChatGPT and other MCP clients.

Sources

Written by Ahmed Shahin, founder of Whathead. Last reviewed 19 November 2026.