screenshots-snapshot-site
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNAPSHOT_SITE_API_KEY | Yes | Your Snapshot Site API key for local stdio mode. | |
| SNAPSHOT_SITE_BASE_URL | No | Base URL for the Snapshot Site API. Defaults to https://api.prod.ss.snapshot-site.com | https://api.prod.ss.snapshot-site.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| screenshotA | Capture a live webpage with Snapshot Site. Use this for screenshots, PDFs, HTML capture, device-sized renders, cookie hiding, custom JS injection, and export retrieval. |
| analyzeA | Capture and analyze a webpage with Snapshot Site. Useful for content summaries, SEO metadata inspection, headings extraction, and quality signals such as blank pages or captcha detection. |
| compareA | Compare two live webpage states or two PNG captures and return before, after, diff, plus mismatch metrics. Useful for QA, release review, and visual regression workflows. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have distinct core purposes (capture, analyze, compare), but 'screenshot' and 'analyze' both involve capturing a live webpage, which could cause confusion. Descriptions provide enough clarity, but the overlap is noticeable.
All tool names are single-word verbs—screenshot, analyze, compare—following a consistent and predictable pattern. There is no mixing of conventions or vague naming.
With 3 tools, the server is well-scoped for its purpose of capturing, analyzing, and comparing webpages. Each tool occupies a distinct role, and the count is within the ideal 3–15 range.
The tool set covers the primary workflows: capture (screenshot), analysis (analyze), and comparison (compare). Minor gaps exist, such as no explicit snapshot management or status listing, but these are not critical for the core functionality.