Skip to main content
Glama

Screenshot a web page

screenshot_page
Read-only

Capture how any public web page looks: a 1280x800 JPEG from a real browser, returned as base64 with its SHA-256, the title and the final URL.

Use it to see a page's layout, check that something renders, or hand the image to a vision model. The image is roughly 50-150 KB of base64 in the response.

$0.003 USDC per capture over x402. A page that fails to load or returns an error costs nothing. For signed, timestamped evidence of a page use attest_page instead. Call without payment to get a quote.

When to use: You need to see a page: its layout, whether something renders, or an image for a vision model. Use instead: read_page when you only need the words (smaller and cheaper); attest_page for signed evidence of a page. Parameters: url must be absolute http(s) and public. Returns: a 1280x800 JPEG as base64, its sha256, title and final_url.

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_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of a public page.
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint, but the description adds pricing ($0.003 USDC via x402), the free-on-failure policy, the payment/quote handshake, response payload size (50-150KB base64), and the returned fields. This is exactly the extra context annotations cannot carry.

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?

Well front-loaded—the output spec leads, then behavior, pricing, and routing. Slightly padded by the 'When to use' block restating the same three example use cases already given in the opening paragraph.

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?

No output schema exists, and the description fully compensates by enumerating return fields, image format/dimensions, and payload size. Payment semantics and failure-cost behavior are also covered, so an agent can call it correctly on the first attempt.

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 both parameters are already documented in the schema, including the quote-then-sign payment flow. The description's restatement ('url must be absolute http(s) and public', 'call without payment to get a quote') adds essentially no meaning beyond it; 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?

States a specific verb+resource with concrete output specifics (1280x800 JPEG from a real browser, base64 + SHA-256 + title + final URL). It also explicitly distinguishes itself from the two nearest siblings, read_page and attest_page.

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

Usage Guidelines5/5

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

Gives an explicit 'When to use' block plus a 'Use instead' line naming both alternatives and the conditions that select them (read_page for text-only, attest_page for signed evidence). Nothing is left to inference.

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.