Skip to main content
Glama

Screenshot the current page

browser_screenshot
Read-only

Use for: visual verification — layout, images, charts, CAPTCHA presence, or evidence of page state. Returns a PNG image (JPEG if the PNG exceeds 2.5MB). Don't use when: you only need the page's content or structure — browser_extract and browser_snapshot are far cheaper in tokens. Paid: $0.02 per call via x402 (Base USDC, Solana USDC, or XRPL XRP).

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": {
      "session_id": "<session_id>"
    },
    "name": "browser_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
full_pageNoCapture the full scrollable page instead of the viewport.
session_idYesSession ID. Reuse the same ID to keep cookies, login state and page position across calls; a new ID starts a fresh browser.

Output Schema

NameRequiredDescriptionDefault
urlYes
bytesYes
mime_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so safety is covered. The description goes well beyond them: it discloses the return format (PNG, with JPEG fallback above 2.5MB) and the monetary cost ($0.02 per call via x402 with named payment rails) — exactly the kind of operational context an agent needs before invoking a paid call.

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?

Three tight clauses, front-loaded with the 'Use for' / 'Don't use when' / cost structure. Every sentence — including the cost line — earns its place for a paid, image-returning tool.

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?

An output schema exists, so return values needn't be documented, yet the description still flags the PNG/JPEG format detail. With usage, alternatives, output format, and billing covered, an agent has everything needed to decide and call correctly.

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%, including a good session_id explanation about cookies/login state and the full_page toggle, so the schema already carries parameter meaning. The description adds no parameter-level guidance of its own; 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?

The description opens with a specific verb+resource framing ('Screenshot the current page' via 'visual verification') and enumerates concrete use cases: layout, images, charts, CAPTCHA presence, evidence of page state. It also names the sibling tools (browser_extract, browser_snapshot) it is not, so an agent can disambiguate without opening schemas.

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?

It gives an explicit 'Use for' clause and a matching 'Don't use when' exclusion, routing content/structure needs to browser_extract and browser_snapshot with the reason ('far cheaper in tokens'). Nothing about tool selection 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.

Resources