Skip to main content
Glama

webcap

by io.github.shoutsid-lab
OverviewDiscussionsAdmin

webcap_capture

PAID ($0.001 image/PDF, $0.005 video): turn a URL into a persistent public artifact. png/jpeg/pdf are a screenshot or PDF and include free OG metadata; mp4/webm scroll-record the page as WebM/VP8 (mp4 is a legacy alias). Settles gasless USDC over x402 — but an unpaid call runs free while the rolling per-IP allowance lasts, so just call it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of the page to process, e.g. https://example.com/
formatNoArtifact format, default png. png/jpeg/pdf = screenshot/PDF at $0.001 (POST /v1/x402/capture); mp4/webm = scroll video at $0.005 (POST /v1/x402/video), always recorded as WebM/VP8. The 402 challenge states the exact price for the format you chose.png
fullPageNoImage/PDF only. true captures the whole scrollable page (default false: viewport only).
durationMsNoVideo formats only. Scroll duration in milliseconds, 1-30000; default 5000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / format / description
      Previous value: -"Artifact format, default png. png/jpeg/pdf = screenshot/PDF at $0.001 (POST /v1/x402/capture); mp4/webm = scroll video at $0.005 (POST /v1/x402/video). The 402 challenge states the exact price for the format you chose."New value: +"Artifact format, default png. png/jpeg/pdf = screenshot/PDF at $0.001 (POST /v1/x402/capture); mp4/webm = scroll video at $0.005 (POST /v1/x402/video), always recorded as WebM/VP8. The 402 challenge states the exact price for the format you chose."
  2. Changed4 schema fields changed
    • addedInput schema / properties / durationMs
      Added value: +{
+  "default": 5000,
+  "description": "Video formats only. Scroll duration in milliseconds, 1-30000; default 5000.",
+  "maximum": 30000,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / format / description
      Previous value: -"Screenshot format; one of png, jpeg, pdf. Default png."New value: +"Artifact format, default png. png/jpeg/pdf = screenshot/PDF at $0.001 (POST /v1/x402/capture); mp4/webm = scroll video at $0.005 (POST /v1/x402/video). The 402 challenge states the exact price for the format you chose."
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "png",
-  "jpeg",
-  "pdf"
-]New value: +[
+  "png",
+  "jpeg",
+  "pdf",
+  "mp4",
+  "webm"
+]
    • changedInput schema / properties / fullPage / description
      Previous value: -"true captures the whole scrollable page (default false: viewport only)."New value: +"Image/PDF only. true captures the whole scrollable page (default false: viewport only)."
  3. Changed6 schema fields changed
    • addedInput schema / properties / format / default
      Added value: +"png"
    • changedInput schema / properties / format / description
      Previous value: -"Screenshot format (default png)"New value: +"Screenshot format; one of png, jpeg, pdf. Default png."
    • addedInput schema / properties / fullPage / default
      Added value: +false
    • changedInput schema / properties / fullPage / description
      Previous value: -"Capture the full scrollable page"New value: +"true captures the whole scrollable page (default false: viewport only)."
    • changedInput schema / properties / url / description
      Previous value: -"Absolute http(s) URL to fetch"New value: +"Absolute http(s) URL of the page to process, e.g. https://example.com/"
    • addedInput schema / properties / url / format
      Added value: +"uri"
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the pricing model, gasless USDC settlement over x402, the free-unpaid fallback, included OG metadata, and that video is always encoded as WebM/VP8. It does not say how long the artifact persists or whether calls are idempotent/retryable on a 402.

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

Conciseness4/5

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

Cost is front-loaded and every clause carries information (price, artifact type, payment rail, free path). The single dense paragraph is slightly run-on but has no filler 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?

For a payment-gated tool with no output schema, it covers the cost, settlement, and format behaviors well, which is the critical context. The one real gap is that it never states what the call returns (e.g., an artifact URL), leaving the response shape undocumented.

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 description coverage is 100%, so the baseline is 3. The description adds only marginal extra meaning beyond the schema ("mp4 is a legacy alias") and otherwise restates the per-format pricing and endpoint split already documented on the format property.

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

Purpose4/5

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

The description states a specific verb+resource (turn a URL into a persistent public artifact) and clarifies the artifact types (screenshot/PDF vs scroll video). It does not, however, differentiate itself from plausible siblings like webcap_preview or webcap_og, which an agent would need to pick between.

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?

It gives a directive ("just call it") plus the condition that an unpaid call runs free while the rolling per-IP allowance lasts, which implies when it is cheap to use. But it names no alternatives and gives no explicit when-not-to-use guidance against the seven sibling tools.

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

All webcap toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources