Skip to main content
Glama
Website Screenshot Capture MCP Server

Website Screenshot Capture MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesYour Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
capture_website_screenshotsA

Open each URL in a Chromium browser and save a PNG or JPEG screenshot, full page or window only. Returns one row per URL with the image link, final URL, HTTP status, page title, and image size. Pages that refuse the browser come back as free blocked rows.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

The server exposes exactly one tool, so there is no possibility of misselection or overlap with a sibling tool. Its purpose (batch URL-to-image capture) is stated unambiguously.

Naming Consistency5/5

A single snake_case verb_noun name (capture_website_screenshots) is internally consistent and follows a predictable convention. There is no competing convention to conflict with it.

Tool Count4/5

The domain is genuinely single-operation (batch screenshot capture), so one tool is defensible rather than an oversight. It is on the thin side — no companion tool for retrieving or cleaning up stored images — but not a mismatch for the stated scope.

Completeness3/5

Core capture is well covered, including status, title, final URL, and blocked-page handling, which are good lifecycle signals. However, there is no way to list, fetch, or delete previously saved screenshots, and viewport/timeout/wait configuration is only hinted at, leaving agents at a dead end for any post-capture workflow.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues