get_cro_overview
One call that returns the store's headline funnel, its five largest sized opportunities, recent anomalies, top UX issues, and the pages failing Core Web Vitals.
When to use it
Any broad question — "how is the store doing", "what should I fix first", "give me a CRO audit". It replaces the first four calls of a manual triage sequence, and its howToProceed field names the drill-down tool to run next.
Ask for it like this
You do not name the tool. These are questions that make an assistant reach for it:
How to read the result
- Rank by topOpportunities.monthlyValue, not by the order the sections appear in.
- deviceFunnels carries a z-test against the rest of the store, so a gap between mobile and desktop is either flagged as real or it is not.
- dataQuality.botSharePct tells you how much declared crawler traffic was removed before any of these numbers were computed.
What will make you wrong
Caveats
- Deliberately shallow — the top three to five of each section. It is triage, never the finished analysis.
Parameters
This tool takes no parameters of its own.
Shared parameters it accepts
Documented in full on the tool reference index.
Date window — defaults to the last 30 days.
Every tool also accepts merchantId, which resolves from your connection. You never pass it.
What comes back
JSON. These are the top-level keys; date-scoped tools additionally carry a _meta block with the server date and the data coverage envelope.