Skip to main content
Glama
Angeluis001

Playwright MCP

by Angeluis001

browser_take_screenshot

Read-only

Capture screenshots of web pages or specific elements using Playwright browser automation. Save images in PNG or JPEG format for documentation, testing, or visual reference purposes.

Instructions

Take a screenshot of the current page. You can't perform actions based on the screenshot, use browser_snapshot for actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoImage format for the screenshot. Default is png.png
filenameNoFile name to save the screenshot to. Defaults to `page-{timestamp}.{png|jpeg}` if not specified. Prefer relative file names to stay within the output directory.
elementNoHuman-readable element description used to obtain permission to screenshot the element. If not provided, the screenshot will be taken of viewport. If element is provided, ref must be provided too.
refNoExact target element reference from the page snapshot. If not provided, the screenshot will be taken of viewport. If ref is provided, element must be provided too.
fullPageNoWhen true, takes a screenshot of the full scrollable page, instead of the currently visible viewport. Cannot be used with element screenshots.

Implementation Reference

  • The main handler function that executes the browser_take_screenshot tool logic. It takes a screenshot of the page viewport or specified element using Playwright, saves it to a file, generates explanatory code, and returns a base64-encoded image if supported by the client.
    handle: async (context, params) => {
      const tab = context.currentTabOrDie();
      const snapshot = tab.snapshotOrDie();
      const fileType = params.raw ? 'png' : 'jpeg';
      const fileName = await outputFile(context.config, params.filename ?? `page-${new Date().toISOString()}.${fileType}`);
      const options: playwright.PageScreenshotOptions = { type: fileType, quality: fileType === 'png' ? undefined : 50, scale: 'css', path: fileName };
      const isElementScreenshot = params.element && params.ref;
    
      const code = [
        `// Screenshot ${isElementScreenshot ? params.element : 'viewport'} and save it as ${fileName}`,
      ];
    
      const locator = params.ref ? snapshot.refLocator({ element: params.element || '', ref: params.ref }) : null;
    
      if (locator)
        code.push(`await page.${await generateLocator(locator)}.screenshot(${javascript.formatObject(options)});`);
      else
        code.push(`await page.screenshot(${javascript.formatObject(options)});`);
    
      const includeBase64 = context.clientSupportsImages();
      const action = async () => {
        const screenshot = locator ? await locator.screenshot(options) : await tab.page.screenshot(options);
        return {
          content: includeBase64 ? [{
            type: 'image' as 'image',
            data: screenshot.toString('base64'),
            mimeType: fileType === 'png' ? 'image/png' : 'image/jpeg',
          }] : []
        };
      };
    
      return {
        code,
        action,
        captureSnapshot: true,
        waitForNetwork: false,
      };
    }
  • Input schema validation using Zod for parameters (raw, filename, element, ref) and tool metadata including the name 'browser_take_screenshot', title, and description.
    const screenshotSchema = z.object({
      raw: z.boolean().optional().describe('Whether to return without compression (in PNG format). Default is false, which returns a JPEG image.'),
      filename: z.string().optional().describe('File name to save the screenshot to. Defaults to `page-{timestamp}.{png|jpeg}` if not specified.'),
      element: z.string().optional().describe('Human-readable element description used to obtain permission to screenshot the element. If not provided, the screenshot will be taken of viewport. If element is provided, ref must be provided too.'),
      ref: z.string().optional().describe('Exact target element reference from the page snapshot. If not provided, the screenshot will be taken of viewport. If ref is provided, element must be provided too.'),
    }).refine(data => {
      return !!data.element === !!data.ref;
    }, {
      message: 'Both element and ref must be provided or neither.',
      path: ['ref', 'element']
    });
    
    const screenshot = defineTool({
      capability: 'core',
      schema: {
        name: 'browser_take_screenshot',
        title: 'Take a screenshot',
        description: `Take a screenshot of the current page. You can't perform actions based on the screenshot, use browser_snapshot for actions.`,
        inputSchema: screenshotSchema,
        type: 'readOnly',
      },
  • Exports the screenshot tool for aggregation into the main tools list.
    export default [
      screenshot,
    ];
  • src/tools.ts:26-50 (registration)
    Imports the screenshot tool module and includes it in the snapshotTools array via spread operator.
    import snapshot from './tools/snapshot.js';
    import tabs from './tools/tabs.js';
    import screenshot from './tools/screenshot.js';
    import testing from './tools/testing.js';
    import vision from './tools/vision.js';
    import wait from './tools/wait.js';
    
    import type { Tool } from './tools/tool.js';
    
    export const snapshotTools: Tool<any>[] = [
      ...common(true),
      ...console,
      ...dialogs(true),
      ...files(true),
      ...install,
      ...keyboard(true),
      ...navigate(true),
      ...network,
      ...pdf,
      ...screenshot,
      ...snapshot,
      ...tabs(true),
      ...testing,
      ...wait(true),
    ];
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering the safety profile. The description adds context about the action limitation (can't perform actions based on screenshot) and the viewport vs element screenshot behavior, but doesn't provide details about return format, error conditions, or performance characteristics.

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 consists of just two sentences that are completely front-loaded with essential information. Every word serves a purpose - the first sentence states the core function, the second provides critical usage guidance. There's zero wasted verbiage.

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 read-only tool with comprehensive parameter documentation and clear annotations, the description provides adequate context. The main gap is the lack of output schema, but the description compensates somewhat by clarifying the tool's limitations relative to browser_snapshot. It could benefit from mentioning what the tool returns (presumably an image file reference).

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?

With 100% schema description coverage, the input schema already documents all 5 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline expectation when schema coverage is complete.

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 clearly states the specific action ('Take a screenshot') and resource ('current page'), distinguishing it from sibling tools like browser_snapshot. It provides a precise verb+resource combination that leaves no ambiguity about the tool's function.

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

Usage Guidelines5/5

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

The description explicitly provides when-not-to-use guidance: 'You can't perform actions based on the screenshot, use browser_snapshot for actions.' This gives clear alternative usage context and distinguishes between screenshot capture versus interactive snapshot tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Angeluis001/playwright-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server