Call ads.create_pmax_campaign
Prepare a Google Ads Performance Max campaign — 'set up a performance max campaign', 'create a pmax campaign from our brand'. Create a Google Ads PERFORMANCE MAX campaign for this brand, with the asset group built from its saved words and pictures, and report the asset counts Google read back. Call it on the ask: it raises the approval card, which is the operator's confirmation, and nothing is created unless they approve it there. ⚠️ It is then created PAUSED and stays paused — you cannot start it, and nothing here spends the budget. Say so when you report it. Two saved things decide whether it can run at all: a bidding choice Performance Max accepts, and the Performance Max assets — ads.google_settings reports exactly which are missing. If missing_required_field_types comes back non-empty, say so: the campaign exists but the group cannot serve yet. Reuse the same idempotency_key on a retry — a fresh key mints a second campaign. Not for a Smart campaign — that is ads.create_smart_campaign. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.
Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/ads.create_pmax_campaign
- Auth: HTTP bearer
Headers
Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.
Your key for this write: send the same key when you retry and the first result comes back instead of a second action. Keys are honoured for at least 24 hours. 1–200 visible ASCII characters. Replaces the idempotency_key body field, which still works until 2026-12-31; this action needs a key on one of the two, and the header is the one to send.
Request body
Response
The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.
Changes
No recorded changes to this operation across all 4 revisions of this API.