Skip to main content
Glama
bala2006

laya-browser-mcp

by bala2006
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_take_screenshot

Capture a page or single element as a PNG, JPEG, or WebP image. Use a ref or selector to target specific elements, or get the full scrollable page.

Instructions

Capture a screenshot of the page (or a single element via a ref/selector) as a PNG, JPEG, or WebP image content block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoImage format for the screenshot. Defaults to png.
targetNoOptional element ref (eN) or selector to screenshot instead of the page.
elementNoHuman-readable element description used to obtain permission to interact with the element.
filenameNoOptional file name hint for the client to save the image under.
fullPageNoCapture the full scrollable page instead of just the viewport (ignored for element shots).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries most of the behavioral disclosure burden. It does disclose the output format ('PNG, JPEG, or WebP image content block') and page/element scope, but it does not mention side effects, permissions, or limitations beyond what the schema already states.

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?

A single, front-loaded sentence with no filler. It communicates the action, target scope, and output format efficiently without redundancy.

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?

With all parameters documented in the schema and the output type stated in the description, an agent has enough to invoke this tool correctly. The main gap is routing guidance versus browser_snapshot, but that is a usage concern rather than a missing calling contract.

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%, so the parameters are already fully documented. The description adds no new parameter-level meaning beyond framing the tool, which matches the baseline for high schema coverage.

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 uses a specific verb ('Capture') and clear resource ('the page or a single element'), with output formats spelled out. It is clear and actionable, but it does not explicitly differentiate from sibling tools like browser_snapshot, so it stops 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 Guidelines2/5

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

The description states only what the tool does ('Capture a screenshot...') and gives no guidance on when to prefer it over alternatives such as browser_snapshot. There are no exclusions, prerequisites, or when-not-to-use signals.

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

Deploy Server

Other Tools