Skip to main content
Glama
acrylicfiddle

x402tools MCP Server

Capture Website Screenshot

image.screenshot
Read-only

Capture website screenshots with configurable dark mode, full-page scrolling, element selection, viewport size, and image format options—rendering any URL with precise timing control.

Instructions

Capture a screenshot of any website. Supports dark mode, full-page, and element selection. Costs $0.05 USDC on Base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to screenshot
delayNoWait ms after page load before capture
widthNoViewport width in pixels
formatNoOutput image formatpng
heightNoViewport height in pixels
_paymentNoBase64-encoded signed v2 PaymentPayload (the value you'd put in the PAYMENT-SIGNATURE HTTP header). Use @x402/evm or @x402/fetch to sign locally with your own wallet — your private key never leaves your machine. Get the requirements from a first call without _payment, then retry.
darkModeNoEmulate prefers-color-scheme: dark
fullPageNoCapture full scrollable page
selectorNoCSS selector to capture specific element

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message when the call failed.
resultNoRaw JSON payload returned by the x402 service on a successful, paid call.
networkNoSettlement network for the x402 payment (base).
serviceNoUnderlying x402tools service that handled the call.
encodingNoEncoding of the binary payload (base64).
mimeTypeNoMIME type of the returned binary payload (e.g. image/png, application/pdf).
price_usdcNoPrice charged for this call, in USDC on Base.
requirementsNox402 payment requirements (scheme, network, amount, payTo, asset) when payment_required is true.
payment_requiredNoTrue when the call needs an x402 payment before it will run.
Behavior4/5

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

Annotations declare readOnlyHint=true, destructiveHint=false, and the description aligns. It discloses the $0.05 USDC cost and the two-phase payment flow (call without _payment first, then retry), which is valuable behavioral transparency. However, it doesn't detail failure modes, rate limits, or output format beyond what the output schema covers.

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 dense sentences with zero wasted words. The feature list (dark mode, full-page, element selection) and the cost disclosure deliver maximum information per sentence.

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

Completeness5/5

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

With 100% schema coverage, an output schema present, and readOnly annotations, the description is complete for its complexity. The intentional two-phase payment flow is adequately explained, and the feature set is well covered. No major gaps identified.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining the _payment parameter's workflow (sign locally, call without it first to get requirements, then retry), which significantly aids correct invocation. The two-phase payment protocol is meaningful additional semantics beyond the schema.

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 clearly states the action ('Capture a screenshot of any website') and lists key capabilities (dark mode, full-page, element selection). It distinguishes well from siblings like image.ocr and document.render_pdf, though it doesn't explicitly name alternatives.

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 gives clear context on what the tool does but does not explicitly state when to use it vs alternatives or when NOT to use it among the sibling tools. The pricing disclosure adds useful context for when to deploy (cost-aware decisions), but no alternative tool is named.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/acrylicfiddle/x402tools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server