Summary
You stop describing the change and start looking at it.
The captures are shaped for a model that has to read them: a full page returns as 1072x1072 tiles rather than one tall image, and capture_selector exists so checking one component does not spend pixels on the rest of the page. capture_console covers the other case — the screenshot looks right and the page is throwing errors anyway.
What it is
Four capture tools pointed at a URL: a tiled full-page screenshot, a screencast over a duration, one element matched by CSS selector, and the console messages a page emits.
What you get
- Full pages captured and tiled into 1072x1072 chunks
- A screencast over a duration you set, with frame intervals that adapt — 100ms up to 5s, 200ms from 5-10s, 500ms beyond that
- PNG frames, or an animated WebP that pauses 4 seconds at the end for looping
- One element captured by CSS selector, with selectorTimeoutMS for elements that arrive late
- Console output collected over a duration that defaults to 4 seconds, with an optional JS command run first
- Viewport width and height set per call, and a waitUntil condition before the capture fires
Requirements
Npx on your PATH. No account and no key.
Setup effort
One command — npx -y @just-every/mcp-screenshot-website-fast