ads

Call ads.attach_audience

Aim a live ad set at one of this brand's audiences — 'target this ad set at our returning customers audience'. Point a live ad set at one of this brand's audiences. It REPLACES whatever audiences that ad set is targeting, and it changes who a live budget reaches — so it needs a person to approve first. If it comes back waiting for approval, say exactly that and do not describe the ad set as changed. Not for creating the audience itself — that is ads.build_audience.

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.

post/api/v1/tools/ads.attach_audience

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/ads.attach_audience
  • Auth: HTTP bearer

Headers

x-request-idstring

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.

Request body

audience_idstring uuid required

The audience's id, as listed on the audiences page.

ad_set_idstring required

The ad set's id on the ad platform.

workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

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.

OR

Changes

No recorded changes to this operation across all 6 revisions of this API.