Skip to main content
Glama

Screenshot

browser_screenshot
Read-only

Captures a JPEG of the current browser viewport when visual layout or images matter, letting an agent inspect page appearance instead of relying on text-only snapshots.

Instructions

JPEG of the current viewport. Prefer browser_snapshot (cheaper, has refs); use this when layout or images matter.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, and non-destructive, so the safety profile is covered. The description adds real value beyond them: the output is a raster JPEG rather than a text tree, and it is scoped to the current viewport rather than the full page. It does not mention size, encoding, or cost beyond the relative comparison, which is a minor gap.

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?

Two compact clauses: the output is front-loaded, then the routing rule follows. Every word carries information — format, scope, alternative, cost, and use case — with no filler.

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

Completeness4/5

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

For a zero-parameter, no-output-schema tool the definition covers what it returns and when to choose it, which is the decision-relevant information. Only fine details of the returned image (dimensions, encoding, whether it is attached as content) are left unstated, which is acceptable here.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. Nothing in the text misleads about inputs.

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 states the concrete output artifact and scope: 'JPEG of the current viewport.' That is enough for an agent to know it produces a raster image of what is currently visible, and it is explicitly contrasted with browser_snapshot. It lacks an explicit action verb, which keeps it just short of 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 Guidelines5/5

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

It names the alternative (browser_snapshot), gives the selection conditions on both sides — cheaper and ref-bearing versus needed when layout or images matter — and implies the default is the snapshot tool. No further routing guidance is needed for a two-option choice.

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