keyword_research

Call keyword_research.read

Check the keyword sweeps this workspace has already run — 'what keywords have we already researched', 'what's the search volume for this term we looked up'. Read the keyword sweeps this workspace has ALREADY run — the seed term, each keyword's monthly volume and difficulty band (low/medium/high), and the SERP results where the provider returned them. Call this FIRST whenever the operator asks about search demand: a sweep costs credits, and the answer is often one we already bought. A sweep with status partial served the keyword half and not the SERP half — say so rather than reporting the SERP as empty. Not for running a new sweep — that is keyword_research.sweep.

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/keyword_research.read

Request

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

querystring

Optional case-insensitive substring of the seed term. Omit to read the most recent sweeps.

limitinteger

How many sweeps to return. 1-20; defaults to 5.

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 4 revisions of this API.