connections

Call connections.check_ad_account_access

Confirm we actually have access to a brand's shared ad account — 'check if the ad account access came through', 'did they finish sharing the ad account'. Ask the platform what access we ACTUALLY have on this brand's ad account right now, and record the answer. Call it when the operator says they have finished sharing the account, or asks whether it came through. It needs their ad account id already on file — connections.ad_account_status shows whether we have one. On TikTok this is what catches the common failure: TikTok's default sharing level is view-only, so a shared account often arrives with access that cannot run campaigns, and this check surfaces the step that fixes it. It only LOOKS: nothing is changed on their ad account, nothing is spent, and the only thing written is our own record of what came back — so it is always safe to run again. Not for asking the platform for access — that is connections.request_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.

post/api/v1/tools/connections.check_ad_account_access

Request

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

platform'meta' | 'google' | 'tiktok' | 'linkedin' required

Which advertising platform's ad account to set up on that platform's own account — the customer owns the account and grants us access to it. The allowed values are the enum's; do not offer a platform outside it.

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.