Call connections.clear_page_cta
Take the call-to-action button off this brand's Facebook Page — 'remove the button on our Facebook Page', 'take off the call-to-action'. Remove the call-to-action button from this brand's Facebook Page entirely. The button disappears from the live Page where the brand's own customers can see it is gone, and nothing here can put it back without being told what it was — so it PREPARES the removal and stops: it shows the operator the button it is about to take off, and only their approve removes it. Not for swapping in a different button — that is connections.set_page_cta. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.
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.clear_page_cta
- 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.