get_page_dom_snapshot
The real rendered DOM of pages visitors actually loaded, pruned to structural elements with classes, IDs, text and nesting.
When to use it
The cheapest way to look at a page. Captured at visit time, so it needs no browser and reflects what shoppers saw rather than what the theme file says.
Ask for it like this
You do not name the tool. These are questions that make an assistant reach for it:
What is actually on my product page?
Show me the structure of my footer.
How to read the result
- Nodes are compact: t is tag, id is id, c is classes, r is role, txt is text, hr is href.
- Use section to zoom into one part of the page — FOOTER, product-section, hero — and maxDepth to cut the tree short.
- Pairing this with get_element_click_analysis answers most UX questions without opening a browser.
What will make you wrong
Caveats
- A snapshot is historical. Open a live browser when you need computed styles, exact pixel layout, interactive state, or proof that the page is still like this.
Parameters
url
Restrict to URLs containing this string, for example /products/blade-kit.
maxDepth
Prune children beyond this tree depth.
section
Zoom into a section by tag, class or ID.
limit
Maximum snapshots to return.
Shared parameters it accepts
None. This tool is not date-scoped — it reports current state rather than a window.
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.
snapshots
One pruned DOM tree per captured page.
format
The key legend for the compact node format.