Skip to main content
Glama

web_tools_screenshot

[$x402 pago por llamada] Captura un screenshot PNG de una página real, vía un navegador headless (Chromium sobre protocolo CDP). Espera ~2s tras navegar antes de capturar.

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": "web_tools_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL completa (http:// o https://), máx. 2000 caracteres.
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral context. It usefully discloses that the call is paid per use via x402, uses a headless Chromium browser over CDP, and waits about 2 seconds after navigation before capturing. However, it omits important screenshot behavior such as viewport vs full-page capture, timeouts, and error handling.

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?

The description is two sentences and front-loads the paid-call marker and core action. Every clause adds useful information with no filler.

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

Completeness3/5

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

The description covers the payment model, rendering engine, waiting behavior, and PNG output, which is enough to understand the basic call. Since there is no output schema and no annotations, it should say more about screenshot scope and output characteristics, such as whether it is viewport or full-page and what happens on rendering failures.

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 schema already fully documents both the required url and optional x_payment parameters. The description adds no parameter-level detail beyond reinforcing the per-call payment model.

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 states a specific verb and resource: capture a PNG screenshot of a real page via a headless Chromium browser over CDP. It is clearly distinguishable from sibling tools such as web_tools_pdf_export or web_tools_extract_article because it explicitly produces a visual screenshot.

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?

Usage is implied by the action description, but there is no explicit guidance on when to choose this tool over alternatives like web_tools_pdf_export or web_tools_extract_article. It also does not state exclusions or prerequisites beyond the payment marker.

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.

Resources