Page Snapshot

New in v3.3.0. get-page-snapshot returns one normalized digest of a page so an agent can reason about it from a single call instead of chaining get-page-structure + get-global-settings + list-global-classes and reassembling the pieces itself. It’s the read foundation the other v3.3.0 features build on.

Read-only, edit_posts, always-on, enabled by default.

emcp-tools/get-page-snapshot

Input:

• post_id (required)
• include (optional), heavy opt-in audit sections: ["performance", "a11y", "seo"]. Default [].
• sections (optional): subset the core sections to control token cost. Default: all.
• fresh (optional): bypass the heavy-section cache.

Core sections (free, computed in-process):

Section	What it contains
post	id, title, slug, status, type, url, builder (elementor/gutenberg/classic), elementor_version
structure	normalized tree (id, kind, widget_type, label, depth, children) + counts (by_widget_type, max_depth, total_elements)
tokens	global colors / typography / g- classes actually in use, each with a usage count, plus raw fonts_in_use / colors_in_use
responsive	which elements carry per-device (tablet/mobile) overrides + rollup counts
content	heading outline, word count, image count, images-missing-alt, link/button counts
seo_lite	h1 count, meta title/description, canonical, og:image (Yoast / Rank Math / core)
warnings	structural smells (empty containers, excessive nesting, missing H1)

Opt-in heavy sections (only when named in include):

• performance: page-level score/grade + top findings from the Performance Analyzer. Free (needs manage_options).
• a11y: accessibility audit summary. Pro (returns pro_gated: true on free builds).
• seo: deep SEO audit summary. Pro (returns pro_gated: true on free builds).

Heavy sections are transient-cached (~15 min); pass fresh: true to recompute.

Why it matters

The snapshot replaces the parse-and-reassemble dance an agent otherwise does across four+ read tools. It’s cheaper (one call, light by default), and it’s the substrate the AI reasons over before editing, feeding cleanly into content search (reuse) and change history (undo).

1. get-page-snapshot          → understand the whole page at once
2. search-content "hero"      → find something similar to reuse
3. update-widget / build-page → make the change
4. list-changes / History tab → review & roll back if needed