Skip to main content
Glama

browser_shot

Capture the page viewport as a PNG; use a URL substring filter to scope the screenshot to the intended page target.

Instructions

Capture the page viewport as PNG. Pass --url-contains to scope capture to one page target.

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": {
      "out": "<out>"
    },
    "name": "browser_shot"
  }
}

Input Schema

NameRequiredDescriptionDefault
outYes
portNo
dry_runNo
protocolNocdp
host_headerNoBiDi Host header; use localhost:9222 through SSH forwarding
url_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden and falls well short. It omits critical behavior: dry_run defaults to true, so the tool presumably reports rather than captures unless explicitly overridden, and nothing is said about whether the file is overwritten, what path is used, or whether capture waits for page load.

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?

Two short sentences, front-loaded with the core action and no wasted wording. The flag-style naming is a minor blemish but the structure is efficient.

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

Completeness2/5

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

A six-parameter mutation tool with no annotations and no output schema needs substantially more: what out should contain, how dry_run behaves, and what the capture returns. The description covers a fraction of what an agent needs to call it correctly.

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

Parameters2/5

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

Schema description coverage is only 17%, and the description explains just one of six parameters, referring to it as the CLI flag "--url-contains" rather than the schema's url_contains. The required out parameter (the output destination) is never described, nor are port, protocol, or dry_run.

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?

States a specific verb and resource — "Capture the page viewport as PNG" — which is clear and distinct from action siblings like browser_click or browser_type. It does not, however, distinguish itself from capture_window, which an agent could plausibly confuse it with.

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

Usage Guidelines2/5

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

The only usage hint is that --url-contains scopes capture to one page target, which is a parameter note rather than when-to-use guidance. There is no statement of prerequisites (must a browser be launched first?), no guidance versus capture_window or browser_scan, and no exclusion conditions.

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