Screenshots of a website
take_screenshotsCapture screenshots of a website's key pages in desktop, mobile and full-page sizes by opening it in a headless browser, hiding cookie banners and floating boxes, and saving organized files.
Instructions
Use it when the user wants screenshots of a site, App Store or Google Play screenshots, Product Hunt gallery images, or a web app manifest's screenshots. Opens a website in a headless browser, picks the pages worth showing (home, pricing, features and the like), hides cookie banners, chat bubbles and other floating boxes, and saves desktop, phone and whole-page screenshots in one folder. sheet.png, every page on one picture, is the picture to show first; SCREENSHOTS.md lists each page with why it was picked, its files and its headings. url and page are pages of one public site: a #route, like /app/#/plants, opens that view of a web app, nothing behind a login is reached, and above one page it starts at the site's root. clean hides everything fixed on the screen but a top bar and a side bar, so an app's own tab bar too. iphone is 1320x2868, the App Store's 6.9 inch size; mobile is 1080x1920, for Google Play phones. For the Google Play feature graphic and Chrome Web Store tiles, use make_launch_stills instead. For a view behind a click, use record_demo_video with steps. The screenshots playbook (makersmcp_playbook) has the whole job. (easyscreenshotkit 0.1.3, on this machine.)
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"url": "<url>"
},
"name": "take_screenshots"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pwa | No | Also save screenshots for a web app manifest in pwa/: each page's first screen at 1920x1080 and on a phone at 1080x1920, at most 8 in all, checked against Chrome's rules for its richer install dialog, with the manifest entries in pwa/manifest-screenshots.json. | |
| url | Yes | The website, like https://linear.app, or a page of it. A #route in it, like https://acme.app/app/#/plants, opens that view of the app; another fragment, like #pricing, is left out. | |
| hide | No | CSS selectors of more elements to hide, like .promo-bar, when something still covers a page. | |
| lang | No | The site's version in this language, when it has one: a language code like de, tr or pt-BR. | |
| page | No | Pages of the same site to take too, like /pricing, or views of a web app by their #route, like /app/#/plants; #/plants alone is that view of url. Each counts toward pages and is taken even past it, and with pages 1 only url and these are taken. Another fragment, like #pricing, is left out. | |
| clean | No | Set to false to take the pages as they come; hide still hides what it names. Otherwise cookie banners, chat bubbles and everything else fixed on the screen are hidden, except a bar along its top and a tall bar down a side, so an app's own bottom tab bar is hidden too. | |
| pages | No | How many pages, the home page included (default 5). Above 1 the site's root comes first, then url when it is a deeper page, then each page, then pages from the site's menu. With 1, only url is taken, though a page that is not of the site still stops the run. | |
| sizes | No | Any of desktop (3200x1800), mobile (1080x1920, a Google Play phone screenshot), iphone (1320x2868, the App Store's 6.9 inch size), full (the whole page at 1x), mobile-full (the whole phone page at 2x), or WxH from 240 to 3840 a side, like 1270x760 for a Product Hunt gallery image. Each takes an optional @scale from 0.5 to 4, and each size goes in once (default desktop, mobile and full). | |
| theme | No | The site's light or dark look, or both, which adds a -dark twin of every picture (default light). A site without a dark theme looks the same in both. | |
| out_dir | No | Folder to save into, absolute or relative to /app. Default: easyscreenshotkit-<host>, where <host> is the site's host without www or the port. A run replaces what an earlier run of this tool left there once it has ended well, and one that fails or is canceled leaves it as it was: give each version its own out_dir. The folder must be empty or hold an earlier run of this tool: any other folder stops it. | |
| wait_seconds | No | How long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them. | |
| reduced_motion | No | Ask the site for its reduced-motion version. | |
| timeout_seconds | No | Give up after this many seconds (default 300). A run takes two or three minutes, up to five on very long pages, and a slow site can take 600. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kit | Yes | ||
| docs | No | The notes the text shows, and where each one is. | |
| next | No | What to do next, as the Next line says. | |
| tool | Yes | ||
| files | No | ||
| folder | No | Where the kit saved its files. | |
| job_id | Yes | ||
| passed | No | For checks: whether the check passed. | |
| status | Yes | ||
| continued | No | True when this call continued the job of an identical call whose answer did not reach the client, instead of starting another. | |
| exit_code | No | ||
| last_line | No | What the kit was doing last. | |
| expires_at | No | When the download links stop working. | |
| next_action | No | ||
| elapsed_seconds | Yes |