Skip to main content
Glama
ToolSnap-app

ToolSnap MCP

by ToolSnap-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Screenshot a URL

screenshot_url

Capture a webpage screenshot at a chosen viewport or full-page size and return a public image URL for sharing, review, or embedding.

Instructions

Screenshot a page → public image URL. $0.04/call. Paid: calling without a payment payload returns a structured 402 with payment options — that response is the documented behavior, not a failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPage URL.
widthNoViewport px.
formatNoDefault png.png
heightNoViewport px.
qualityNoJPEG only, 1-100.
fullPageNotrue = whole page, not viewport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • changedInput schema / properties / format / description
      Previous value: -"Image format: \"png\" (default) or \"jpeg\"."New value: +"Default png."
    • changedInput schema / properties / fullPage / description
      Previous value: -"Capture the entire scrollable page instead of just the viewport. Default false."New value: +"true = whole page, not viewport."
    • changedInput schema / properties / height / description
      Previous value: -"Viewport height in pixels (default 800, 100–4000). Ignored when fullPage is true."New value: +"Viewport px."
    • changedInput schema / properties / quality / description
      Previous value: -"JPEG quality 1–100 (only applies when format is jpeg)."New value: +"JPEG only, 1-100."
    • changedInput schema / properties / url / description
      Previous value: -"The URL of the page to screenshot (http:// or https://)."New value: +"Page URL."
    • changedInput schema / properties / width / description
      Previous value: -"Viewport width in pixels (default 1280, 100–4000)."New value: +"Viewport px."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing per-call cost ($0.04) and explicitly framing the 402 payment-required response as expected behavior rather than an error — a real trap for an agent. It stops short of describing rate limits, timeouts, or what the image URL looks like/expires.

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?

One compact line with the core action front-loaded, followed by cost and the non-failure 402 semantics in priority order. No wasted sentences.

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?

Covers the essentials an agent needs for a 6-param, no-output-schema tool: what comes back (a public image URL) and how billing/payment surfaces. Parameter details are fully handled by the schema, leaving only minor gaps like URL lifetime and error conditions other than 402.

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%, so width, height, format, quality, and fullPage are already documented with defaults and constraints. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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?

"Screenshot a page → public image URL" names a specific verb, resource, and the shape of the output, which cleanly separates it from the fetch_* and conversion siblings. An agent knows exactly what it gets back without opening the schema.

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

Usage Guidelines3/5

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

The description clarifies the paid call model and what a 402 response means, which is genuinely useful usage context. It does not say when to prefer this over fetch_html or other rendering tools, so the alternative-selection guidance is only implied.

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

Deploy Server

Other Tools