WebsiteScreenshot.online MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCREENSHOT_API_KEY | Yes | The WebsiteScreenshot.online API key (Bearer token) required to authenticate requests. | |
| SCREENSHOT_API_BASE | No | Override the API base URL for self-hosted or staging instances. Defaults to https://websitescreenshot.online. | https://websitescreenshot.online |
| SCREENSHOT_REQUEST_TIMEOUT_MS | No | Per-request abort timeout in milliseconds. Defaults to 60000. | 60000 |
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 |
|---|---|
| take_screenshotA | Capture a PNG/JPEG/PDF screenshot of any public URL via WebsiteScreenshot.online. Returns the public image URL (24h TTL) and metadata. Use fullSize=true for full-page captures. |
| record_website_videoA | Record a scrolling webm/mp4/gif capture of any public URL. Returns the public video URL (24h TTL). Pass async=true to receive a requestId; poll check_video_status until status=completed or status=error. |
| check_video_statusA | Poll the status of an async video job created by record_website_video(async=true). |
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
Each tool has a clearly distinct role: take_screenshot captures an image, record_website_video captures a video, and check_video_status polls an async video job. There is no ambiguity about which tool to select for a given task.
All tool names follow a consistent snake_case verb_noun pattern: take_screenshot, record_website_video, check_video_status. The pattern is predictable and clearly indicates the action being performed.
Three tools is well-scoped for a screenshot/video capture server: one for screenshots, one for video, and one for async status polling. Each tool earns its place without unnecessary redundancy.
The core capture lifecycle is covered: synchronous screenshot capture, synchronous or asynchronous video capture, and async job polling. Minor gaps exist such as listing or canceling active video jobs, but the main workflows are fully usable.