Skip to main content
Glama

browser_take_screenshot

Read-only

Capture screenshots of web pages or specific elements using Playwright MCP. 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.
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 handler function that implements the logic for taking screenshots of the page viewport, full page, or specific elements using Playwright.
    handle: async (tab, params, response) => {
      const fileType = params.type || 'png';
      const fileName = await tab.context.outputFile(params.filename ?? `page-${new Date().toISOString()}.${fileType}`);
      const options: playwright.PageScreenshotOptions = {
        type: fileType,
        quality: fileType === 'png' ? undefined : 90,
        scale: 'css',
        path: fileName,
        ...(params.fullPage !== undefined && { fullPage: params.fullPage })
      };
      const isElementScreenshot = params.element && params.ref;
    
      const screenshotTarget = isElementScreenshot ? params.element : (params.fullPage ? 'full page' : 'viewport');
      response.addCode(`// Screenshot ${screenshotTarget} and save it as ${fileName}`);
    
      // Only get snapshot when element screenshot is needed
      const locator = params.ref ? await tab.refLocator({ element: params.element || '', ref: params.ref }) : null;
    
      if (locator)
        response.addCode(`await page.${await generateLocator(locator)}.screenshot(${javascript.formatObject(options)});`);
      else
        response.addCode(`await page.screenshot(${javascript.formatObject(options)});`);
    
      const buffer = locator ? await locator.screenshot(options) : await tab.page.screenshot(options);
      response.addResult(`Took the ${screenshotTarget} screenshot and saved it as ${fileName}`);
      response.addImage({
        contentType: fileType === 'png' ? 'image/png' : 'image/jpeg',
        data: buffer
      });
    }
  • Zod schema defining the input parameters for the browser_take_screenshot tool, including validations for element screenshots and full page options.
    const screenshotSchema = z.object({
      type: z.enum(['png', 'jpeg']).default('png').describe('Image format for the screenshot. Default is png.'),
      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.'),
      fullPage: z.boolean().optional().describe('When true, takes a screenshot of the full scrollable page, instead of the currently visible viewport. Cannot be used with element screenshots.'),
    }).refine(data => {
      return !!data.element === !!data.ref;
    }, {
      message: 'Both element and ref must be provided or neither.',
      path: ['ref', 'element']
    }).refine(data => {
      return !(data.fullPage && (data.element || data.ref));
    }, {
      message: 'fullPage cannot be used with element screenshots.',
      path: ['fullPage']
    });
  • Tool registration using defineTabTool, specifying the name 'browser_take_screenshot', schema, description, and handler.
    const screenshot = defineTabTool({
      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',
      },
    
      handle: async (tab, params, response) => {
        const fileType = params.type || 'png';
        const fileName = await tab.context.outputFile(params.filename ?? `page-${new Date().toISOString()}.${fileType}`);
        const options: playwright.PageScreenshotOptions = {
          type: fileType,
          quality: fileType === 'png' ? undefined : 90,
          scale: 'css',
          path: fileName,
          ...(params.fullPage !== undefined && { fullPage: params.fullPage })
        };
        const isElementScreenshot = params.element && params.ref;
    
        const screenshotTarget = isElementScreenshot ? params.element : (params.fullPage ? 'full page' : 'viewport');
        response.addCode(`// Screenshot ${screenshotTarget} and save it as ${fileName}`);
    
        // Only get snapshot when element screenshot is needed
        const locator = params.ref ? await tab.refLocator({ element: params.element || '', ref: params.ref }) : null;
    
        if (locator)
          response.addCode(`await page.${await generateLocator(locator)}.screenshot(${javascript.formatObject(options)});`);
        else
          response.addCode(`await page.screenshot(${javascript.formatObject(options)});`);
    
        const buffer = locator ? await locator.screenshot(options) : await tab.page.screenshot(options);
        response.addResult(`Took the ${screenshotTarget} screenshot and saved it as ${fileName}`);
        response.addImage({
          contentType: fileType === 'png' ? 'image/png' : 'image/jpeg',
          data: buffer
        });
      }
    });
Behavior4/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false, establishing this as a safe read operation. The description adds valuable context about the limitation that screenshots can't be used for actions, which goes beyond what annotations convey. However, it doesn't mention potential limitations like size constraints or performance implications.

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 perfectly front-loaded: the first states the core purpose, the second provides critical usage guidance. Every word serves a purpose with zero redundancy or unnecessary elaboration.

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 operation with comprehensive parameter documentation in the schema, the description provides sufficient context about purpose and limitations. The main gap is the lack of output schema, but the description adequately covers the tool's scope given its annotations and sibling context. It could benefit from mentioning return format or typical use cases.

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 comprehensively documents all 5 parameters. The description doesn't add any parameter-specific information beyond what's already in the schema. The baseline score of 3 reflects adequate parameter documentation through the schema alone.

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 which is mentioned for actions. 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 and distinguishes between screenshot capture (this tool) and interactive snapshots (sibling tool).

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/maywzh/playwright-mcp'

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