screenshotfreeapi
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCREENSHOTFREEAPI_KEY | Yes | Your API key (sfa_...). Without it, every tool call fails with 401. | |
| SCREENSHOTFREEAPI_BASE_URL | No | Override the API base URL. Defaults to https://api.screenshotfreeapi.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 |
|---|---|
| screenshot_webA | Capture a screenshot of any public website URL. Supports AI-targeted sections, full-page capture, PDF export, and custom viewport dimensions. Returns a presigned URL to the screenshot image. |
| screenshot_mobileA | Fetch app store listing screenshots for any iOS or Android app by name or bundle/package ID. Returns screenshots from Google Play and/or the Apple App Store along with rich metadata (version, rating, reviews, category). |
| render_htmlA | Render a raw HTML string (email template, certificate, report card, etc.) to a screenshot image. Requires STARTER plan. |
| get_job_statusA | Poll the current status and progress of a screenshot job. Status values: queued → processing → completed | failed. |
| get_job_resultA | Retrieve the screenshot URLs and metadata for a completed job. Returns presigned URLs (15-minute TTL). Returns an error if the job is still in progress. |
| list_jobsA | List recent screenshot jobs for the authenticated API key. Filter by status or type. |
| check_quotaA | Check the remaining screenshot quota and current plan for the authenticated API key. |
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 7 tools
Each tool targets a distinct aspect of the screenshot service: quota checking, job management (listing, status, results), and three distinct screenshot sources (web, mobile, HTML). No two tools have overlapping functionality.
Tool names generally follow a verb_noun pattern (check_quota, get_job_result, get_job_status, list_jobs, render_html), but screenshot_mobile and screenshot_web use a noun-verb style. This minor inconsistency reduces the score slightly.
With 7 tools, the server is well-scoped for its purpose: it covers screenshot generation from multiple sources, job tracking, and quota checking without unnecessary clutter.
The tool surface covers the core screenshot workflow (create, track, retrieve) and multiple input types. Minor gaps include no way to cancel/delete jobs or manage API keys, but these are not critical for basic usage.