Call connections.complete_ad_account_step
Mark one guided setup step as done — because the OPERATOR SAID THEY DID IT, as in 'I've done that step' or 'I added you as a partner' — and advance to the next. Only call this when they have told you they finished that step; it records their word, and we have no way to check it for them. Nothing is sent to the platform. One step per platform also asks for the operator's own ad account id — pass external_account_id there, and ask them for it if you do not have it. Call connections.ad_account_status first to see what is outstanding. There is NO tool that un-marks a step: if they need to redo one, tell them to open Connections and use “Start the steps again”, which re-opens the setup without losing the steps they already finished. Not for checking whether the access actually came through — that is connections.check_ad_account_access.
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/connections.complete_ad_account_step
- 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.
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 6 revisions of this API.