ZuckerBot › Tool reference › Strategy & campaign build
zuckerbot_launch_campaign
| Name | Type | Description | |
|---|---|---|---|
campaign_id | string | required | ZuckerBot campaign ID from the create step |
meta_access_token | string | optional | User's Meta/Facebook access token. Optional if Facebook is connected on zuckerbot.ai |
meta_ad_account_id | string | optional | Meta ad account ID (format: act_XXXXX). Optional if Facebook is connected on zuckerbot.ai |
meta_page_id | string | optional | Facebook Page ID. Optional if Facebook is connected on zuckerbot.ai |
variant_index | number | required | Which creative variant to launch (0-indexed) |
daily_budget_cents | number | optional | Override daily budget in cents |
radius_km | number | optional | Override targeting radius in km |
launch_all_variants | boolean | optional | Launch all creative variants as separate ads for A/B testing. Meta will auto-optimize for the winner. |
{
"tool": "zuckerbot_launch_campaign",
"arguments": {
"campaign_id": "<campaign_id>",
"variant_index": 123
}
}
You never invoke this directly — describe what you want in plain English inside Claude, Cursor, ChatGPT or any MCP client with ZuckerBot connected, and the agent selects zuckerbot_launch_campaign and fills the arguments for you.