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

playwright-mcp-server

by doucej
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

screenshot

Capture a PNG snapshot of the current page or a specific element. Specify a CSS selector for targeted capture or enable full_page to include the entire scrollable page.

Instructions

Capture a PNG screenshot of the current page or a specific element.

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": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorNoOptional CSS selector — captures only that element instead of the page.
full_pageNoCapture the full scrollable page, not just the viewport (default: false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It states the output is a PNG screenshot and the scope (page or element), but does not mention side effects (likely none) or return format details (e.g., base64 or file). This is a minor gap given the simple nature of the operation.

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?

Single sentence, front-loaded with the action, zero waste. Perfectly concise.

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?

The tool has 2 optional params and no output schema. The description plus schema provides clear scope and options. It does not explicitly state how the PNG is returned, but for a simple capture tool this is adequate. The sibling context doesn't require additional caveats.

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 baseline is 3. The description does not add parameter semantics beyond the schema, but the schema already fully documents both optional parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 clearly defines the resource ('the current page or a specific element'), and specifies the output format (PNG). This distinguishes it from other browser automation tools since no sibling tool captures screenshots.

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

Usage Guidelines4/5

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

The description implies when to use it (when a screenshot is needed) but does not provide explicit exclusions or alternative tool mentions. Since no other tool in the sibling list handles screenshots, this is sufficient guidance.

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