Skip to main content
Glama

snapforge

by org.snapforge

SnapForge screenshot

snapforge_screenshot
Read-only

Capture a screenshot of a public URL or raw HTML as a PNG/JPEG image. Full-page by default. Requires a SnapForge API key (no key? call snapforge_signup first).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPublic http/https URL to render. Provide either url or html.
htmlNoRaw HTML to render instead of a URL (max 2MB). Provide either url or html.
delayNoExtra wait in milliseconds before capture (0–10000)
scaleNoDevice pixel ratio for high-DPI/retina output (1–3)
widthNoViewport width in pixels (100–3840)
formatNoImage format: "png" (default) or "jpeg"
heightNoViewport height in pixels (100–2160)
qualityNoJPEG quality 1–100 (ignored for PNG)
fullPageNoCapture the full scrollable page (default true)
waitUntilNoWhen to consider the page ready: "load" (default) or "networkidle"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bytesYesSize of the returned image in bytes
mimeTypeYesImage MIME type, e.g. image/png

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate read-only and open-world behavior. Description adds capture context (full-page, API key) but does not disclose rate limits or other constraints. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with all key information front-loaded. No redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given high parameter count (10) but full schema coverage and output schema present, description covers purpose, prerequisites, and defaults adequately. Could mention output schema briefly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions per parameter. Description adds no extra parameter semantics beyond mentioning URL vs HTML choice and default format. Baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool captures a screenshot from a URL or raw HTML as PNG/JPEG, mentions full-page default, and distinguishes from siblings by requiring SnapForge API key. Specific verb and resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly mentions API key prerequisite and suggests signup alternative, provides default behavior (full-page). Does not explicitly state when not to use, but context with siblings is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All snapforge toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: markdown extraction, PDF rendering, screenshot capture, and account signup. No overlap or ambiguity.

Naming Consistency5/5

All tools follow the same 'snapforge_<format>' pattern, making them predictable and easy to distinguish.

Tool Count5/5

Four tools is well-scoped for a service that converts URLs/HTML to different formats plus a signup process. Neither sparse nor excessive.

Completeness4/5

Covers the core conversion tasks (markdown, PDF, screenshot) and the necessary signup flow. Minor missing features like configurable screenshot options, but no major gaps for the stated purpose.

Resources