APIScreenshot
Server Details
Screenshot any URL or HTML as PNG/JPEG/WebP from your AI agent. Full-page, clean, no install.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion among tools.
The single tool name 'take_screenshot' follows a clear verb_noun pattern, consistent with itself.
The tool count is 1, which is borderline thin for typical MCP servers. While the tool is comprehensive, the surface feels minimal.
The tool covers all necessary screenshot functionality: URL or HTML input, multiple formats, viewport control, and element selection. No obvious gaps.
Available Tools
1 tooltake_screenshotTake ScreenshotAInspect
Capture a screenshot of a live website (by URL) or of inline HTML and return it as an image. Provide exactly one of url or html. Supports full-page capture, PNG/JPEG/WebP output, a custom viewport, and capturing a single element by CSS selector. Requires an API key (Authorization: Bearer) — get one at https://apiscreenshot.com.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Absolute http(s) URL of the page to capture. Provide EXACTLY ONE of `url` or `html`. | |
| html | No | Inline HTML to render and capture instead of navigating to a URL. Provide EXACTLY ONE of `url` or `html`. | |
| format | No | Output image format: 'png' (default, lossless), 'jpeg' or 'webp'. | |
| fullPage | No | Capture the full scrollable page instead of just the viewport. Default false. | |
| selector | No | CSS selector — capture just the first matching element instead of the page. | |
| viewport | No | Browser viewport to render at. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries burden. Mentions authorization and output type, but does not disclose rate limits, file size limits, latency, or error behavior. Adequate but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences that are well-structured and front-loaded. Every sentence adds essential information. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers major features comprehensively given 6 parameters and no output schema. Slightly vague on return format (image) and no mention of error handling, but otherwise complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. Description adds value by clarifying mutual exclusivity of url/html and explaining the viewport object. Goes beyond schema repetition.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it captures a screenshot of a live website or inline HTML. Specifies key features: full-page capture, output formats, custom viewport, and element selection. Distinguishes from missing siblings is not needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says to provide exactly one of url or html. Mentions requirement for API key and where to get it. Does not mention alternatives, but context is clear for correct usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!