Call keyword_research.sweep
Kick off a new keyword sweep on a seed term — 'research keywords for coffee shops near me', 'look up search volume for this term'. Run a NEW keyword sweep on a seed term and file it on a board. This calls a paid provider and CHARGES the workspace credits, so check keyword_research.read first — a sweep we already ran costs nothing to re-read. When the member asked for it themselves it runs; otherwise they see an approve card first. Never say data came back until the tool has returned rows. Not for sweeps already run — that is keyword_research.read. 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/keyword_research.sweep
- 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 8 revisions of this API.