get_top_issues
The store's worst pages by rage-click rate, dead-click rate, bounce rate or scroll depth, each labelled with the issue type.
When to use it
To pick which page to investigate when nothing more specific points you at one.
Ask for it like this
You do not name the tool. These are questions that make an assistant reach for it:
Which pages need attention first?
Show me the pages with the worst rage clicking.
How to read the result
- high_dead_clicks means elements are clicked but have no href or handler — usually a paragraph, list item or decorative div mistaken for a link.
- high_rage_clicks means checking the most-clicked CTA for a sold-out variant, a slow handler or a broken state. Baseline is roughly 5 to 8%.
- low_scroll_depth means looking above the fold for friction — an intrusive popup, a slow hero, a broken CTA.
Parameters
limit
Maximum issues to return.
Shared parameters it accepts
Documented in full on the tool reference index.
Date window — defaults to the last 30 days.
dateFrom
Start of the window, YYYY-MM-DD. Inclusive.
dateTo
End of the window, YYYY-MM-DD. Inclusive.
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.
issues
Per URL: views, bounce rate, rage-click rate, dead-click rate, average scroll depth, and the issue_type that flagged it.