Skip to main content
Glama
Sign In
invisible-playwright-mcp

invisible-playwright-mcp

by solver492
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_take_screenshot

Read-only

Captures an on-demand screenshot of the current browser page, letting you save visual state for review or verification. Choose main or support browser as needed.

Instructions

One screenshot of this browser's page, on demand.

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_take_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
browserNoDefaults to `main`; `support` is the helper beside it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.70.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that this is a single, on-demand capture rather than a continuous watch, but it does not clarify output format, viewport behavior, or whether any page-load waiting occurs.

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?

The description is a single, front-loaded sentence with no filler. Every word adds meaning: 'one', 'screenshot', 'this browser's page', and 'on demand'.

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 simple, read-only, single-parameter tool with annotations covering the safety profile, the description is largely complete. It is slightly incomplete in that it does not mention what the screenshot returns (e.g., image data or a file reference) and does not distinguish itself from browser_snapshot.

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%, and the parameter description already explains the 'main'/'support' browser options and default. The tool description itself adds no further meaning to the parameter, so the schema carries the burden as expected.

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 a specific verb ('take screenshot') and resource ('this browser's page'), making the core action clear. It does not explicitly differentiate from the sibling tool 'browser_snapshot', which could be mistaken for a similar action.

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?

No guidance is given on when to use this tool versus alternatives like browser_snapshot, browser_read_html, or browser_watch. The phrase 'on demand' is the only hint, but it does not explain when a screenshot is preferable or when not to use it.

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