Call seo.serp_features
Break a Google results page down for SEO — 'what's the featured snippet for this term', 'which People Also Ask questions come up for this search', 'which sources does the AI Overview cite here'. A PAID, deep read of the LIVE Google results page for a query. It returns: who ranks organically, whether there is a featured snippet and who holds it, the People-Also-Ask questions, every SERP feature on the page, and Google's AI Overview with the sources it cites. This calls a paid provider and CHARGES the workspace credits, so ask it about the searches the operator actually named rather than exploring. organic carries EVERY result the requested depth bought — nothing is trimmed after the charge — so raise depth when the operator asks about results past the first page and report the whole list you get back. ai_overview.present: true with resolved: false means Google IS writing an answer for this query and the provider could not read it — say exactly that, and never report it as no overview. Not for a plain look at what Google shows or who ranks — that is web.search in 'serp' mode. 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/seo.serp_features
- 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 4 revisions of this API.