Skip to main content
Glama

Screenshot any public web page

screenshot
Read-only

Screenshot any public web page. Returns a JPEG (base64 data URL plus a hosted URL). Options: width (320-2560, default 1280), height (300-8000, default 900), fullPage (boolean). Takes 3-15 s. Price: $0.01 per call (x402, USDC on Base). Without payment, returns the payment requirements.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
widthNoViewport width in px (320-2560)
heightNoViewport height in px (300-8000)
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.
fullPageNoCapture the whole page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds everything an agent actually needs to plan a call: expected latency of 3-15 s, a concrete $0.01/call price in USDC on Base, and the key non-obvious behavior that an unpaid call returns payment requirements rather than an error or an image. Return shape is also disclosed.

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?

Four tight sentences, front-loaded with purpose and return value before cost and payment mechanics. The parenthetical option list slightly restates the schema and the parenthetical price detail packs a lot into one clause, but nothing is padded or redundant at the sentence level.

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 no output schema, the description carries the burden of explaining returns and does so (JPEG, base64 plus hosted URL). Combined with latency, pricing, and the two-step payment negotiation, an agent has enough to call this correctly on the first attempt without trial and error.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: default values for width (1280) and height (900) that the schema does not state, plus confirmation that fullPage captures the whole page. The payment parameter's role is reinforced by the unpaid-first-call instruction.

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 gives a specific verb and resource ("Screenshot any public web page") and even states the output format (JPEG as a base64 data URL plus a hosted URL), so the agent knows exactly what it gets back. It never contrasts itself with content-extraction siblings like page_markdown or page_text, so it falls short of the sibling-differentiation bar for a 5.

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 strongest guidance is the x402 flow: call without payment first to learn the price and requirements, then pass the signed PAYMENT-SIGNATURE. That is genuinely actionable. But there is no guidance on when to choose this tool over page_text/page_markdown, or on which pages merit a screenshot versus text extraction, so usage context is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.