ads

Call ads.plan

Read back the campaign built from the brief answers so far — 'show me the plan', 'what will this campaign look like', 'make it five ads'. Propose the campaign from the answers recorded so far. Pass concept_count only when the person names how many ads they want; without it the plan proposes Goosy's default, and the answer's concept_count is the number planned. This creates nothing and spends nothing — it is the read-back a person accepts, and each planned ad is drawn and paid for only after that. Call it only once every question is answered; it will tell you which one is still open otherwise. Not for accepting the plan once the person agrees — that is ads.accept_plan.

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

Request

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

run_idstring uuid required

The brief's run id, as given in this conversation.

concept_countinteger

How many ads to plan, only when the person names a number ('make it five ads'). Leave it out for Goosy's default. A number past the most one board draws is held to it; the answer's concept_count is what was planned.

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.