ads

Call ads.launch_check

Check whether one campaign is ready to go live — the ad account, a way to pay, where clicks land, the words, what it spends, and whether every ad is drawn. If they say 'this campaign' and name no id, CALL IT WITH NO ARGUMENTS: it resolves the campaign whose page they are on, and refuses plainly when there is none. Never ask which campaign before trying that. It reads only: it changes nothing, approves nothing and launches nothing. Not for drawing or changing the ads, or for whether an approved launch landed ('did it land on Meta?') — those are the campaign's board and ads.read_board.

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.launch_check

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/ads.launch_check
  • 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

campaign_idstring uuid

The campaign's id, as given in this conversation or its URL.

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 4 revisions of this API.