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

mcp-playwright-automation

by pedro95nunes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Screenshot

screenshot

Capture the current page as an image file, saving it to a specified path for visual verification during browser automation.

Instructions

Takes a screenshot of the page

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "filename": "<filename>"
    },
    "name": "screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesFile name (relative to the screenshots/ folder) or absolute path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'takes a screenshot' without revealing whether it captures the full page, waits for resources, scrolls, or has any side effects. This is a significant gap for a tool that likely affects browser state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no fluff, which is concise. However, it is under-specified rather than efficiently structured—it lacks any supporting context or organization that would help an agent use it correctly.

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

Completeness2/5

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

For a browser automation tool, this description is incomplete. It does not specify the output format, whether the screenshot is saved automatically, or any prerequisites like waiting for the page to load. Given the sibling tools and the absence of an output schema, more detail is necessary for correct invocation.

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% (only one parameter, filename, is fully described in the schema). The description adds no extra meaning beyond what the schema already provides, so the baseline of 3 applies.

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 clear verb and resource: 'Takes a screenshot of the page'. This distinguishes it from sibling tools like navigate or click, which have different purposes. However, it lacks specificity about scope (e.g., viewport vs. full-page) or any caveats, so it is clear but minimal.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites like a loaded page, nor does it suggest any exclusions. The description simply states what it does without context.

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