connections

Call connections.ad_account_status

Check where a brand's guided ad-account setup stands — 'where are we with connecting our ad account', 'what's the status of our facebook ads setup'. Read where this brand's guided ad-account setup stands for one platform, and which step is next. Call this before answering anything about ad-account access or advertising setup — never guess the state. Read grant_state carefully: awaiting_platform_access means WE are waiting on the platform to approve our access, so the customer has nothing to do and nothing is wrong with their account; active is the only state that means we can manage their campaigns. Not for whether the advertising authorization is signed — that is connections.agency_authorization_status.

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

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/connections.ad_account_status
  • 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 7 revisions of this API.