Skip to main content
Glama

browser_screenshot

Read-onlyIdempotent

Captures the visible browser viewport for UI verification and debugging, helping you check rendered pages during automated testing.

Instructions

Capture a viewport screenshot (may contain private ERPNext data).

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 observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description's one addition of value is the privacy warning that the capture may contain private ERPNext data, which the agent cannot infer from structured fields. It still omits whether a live browser session is required and what the tool returns (image handle, URL, or inline data).

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?

A single short sentence with no filler, and the core action is front-loaded. The parenthetical privacy note is compact, though it sits at the end where it reads as an afterthought rather than a deliberate warning. Nothing is wasted, but the sentence is near the lower bound of what a tool definition can usefully say.

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 tool is simple (no parameters, no output schema, annotations covering the safety profile), so heavy documentation is not needed. Even so, the definition leaves out the prerequisite that a page must be open and what the caller receives back, which matters for an agent that must decide whether a screenshot is even possible right now.

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?

There are zero input parameters, so there is no parameter meaning for the description to carry, and the baseline of 4 applies. The description correctly does not invent arguments that the schema does not define.

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 a viewport screenshot." That is more precise than a generic "take screenshot" because it scopes the capture to the viewport. It does not distinguish itself from nearby siblings such as browser_snapshot or browser_source_probe, so an agent gets no help choosing among the browser capture tools.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. Nothing tells the agent whether this requires an open page first or when browser_snapshot would be preferred. Usage is only implied by the tool name and the browser_ prefix shared with its siblings.

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