Call connections.agency_authorization_status
Check whether this account has signed the advertising authorization — 'have we signed the ad authorization', 'why can't we set up ad accounts'. Read whether this account has signed the advertising authorization — the written go-ahead we need before asking any advertising platform for access to their ad account. Call this whenever ad-account setup will not proceed, or when asked what we are authorized to do with their advertising. YOU CANNOT SIGN IT: signing is a person reading the document and typing their name on the Connections surface, and there is no tool for it — say what is missing and point them there. Not for the ad-account setup steps themselves — that is connections.ad_account_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.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/connections.agency_authorization_status
- 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 7 revisions of this API.