snaprender-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNAPRENDER_API_KEY | Yes | Your SnapRender API key. You can get one by signing up for free at app.snap-render.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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| take_screenshotA | Capture a screenshot of a website URL, raw HTML, or Markdown content. Provide exactly one of: url, html, or markdown. Returns the image as a PNG, JPEG, WebP, or PDF. Supports device emulation (iPhone, Pixel, iPad), dark mode, ad blocking, cookie banner removal, full-page capture, and custom viewports. |
| check_screenshot_cacheA | Check if a screenshot is already cached without capturing a new one. Does not count against your quota. Pass the same parameters you would use for take_screenshot so the cache key matches correctly. |
| sign_screenshot_urlA | Generate a signed URL for a screenshot that can be used without an API key. Useful for embedding screenshots in emails, documents, or sharing with third parties. Signing is free, rendering the URL consumes one credit. URLs expire after the specified duration. |
| extract_contentA | Extract content from a web page. Returns structured data based on the extraction type. Supports: markdown (readable content), text (plain text), html (raw HTML), article (structured with title/author/excerpt), links (all page links), metadata (OG tags, title, description). |
| batch_screenshotsA | Create a batch screenshot job for multiple URLs (1-50). Returns immediately with a job ID. Use get_batch_status to poll for results (wait 2-5 seconds between polls). All URLs share the same screenshot options. Each URL consumes one credit; failed URLs get credits rolled back. |
| get_batch_statusA | Get the status of a batch screenshot job. Poll this until status is 'completed' or 'failed' (wait 2-5 seconds between polls). Completed items include presigned download URLs valid for 24 hours. |
| list_webhooksA | List all webhook subscriptions on your account. Returns webhook IDs, URLs, subscribed events, and creation dates. |
| create_webhookA | Create a webhook subscription for event notifications. Events: screenshot.completed (batch job done), quota.warning (80% used), quota.exceeded (100% used), capture.completed and change.detected (scheduled captures). Max 5 webhooks per account. Payloads are signed with HMAC-SHA256. Save the returned secret to verify signatures. |
| delete_webhookA | Delete a webhook subscription by ID. This cannot be undone. |
| test_webhookA | Send a test payload to a webhook endpoint to verify it receives events correctly. Returns the delivery status and HTTP response code. |
| get_usageA | Get current month's screenshot usage statistics including screenshots used, limit, and remaining quota. |
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 11 tools
Each tool targets a distinct action+resource: single capture, batch capture, cache check, URL signing, batch polling, content extraction, webhook CRUD/test, and usage. The capture-family tools (take_screenshot, batch_screenshots, extract_content) are clearly differentiated by descriptions covering single vs. bulk vs. structured extraction.
Mostly a consistent verb_noun pattern (take_screenshot, check_screenshot_cache, get_batch_status, extract_content, list_webhooks, create_webhook, delete_webhook, test_webhook, get_usage). The lone deviation is batch_screenshots, which is noun-first but still readable and unambiguous.
11 tools is well within the sweet spot for a screenshot/rendering service, with each tool covering a distinct capability (capture, batch, cache, signing, extraction, webhooks, usage). No tool feels redundant or padded.
Covers the core lifecycle: single/batch capture, cache check, signed sharing, content extraction, webhook management, and usage reporting. Minor gaps exist such as no batch cancel/list or update_webhook (delete-and-recreate is the workaround), but no workflow dead-ends.