Skip to main content
Glama
JustasMonkev

MCP Accessibility Scanner

browser_take_screenshot

Read-only

Capture screenshots of web pages or specific elements for accessibility analysis. Supports JPEG or PNG formats, enabling detailed visual reports for WCAG compliance testing.

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
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.
filenameNoFile name to save the screenshot to. Defaults to `page-{timestamp}.{png|jpeg}` if not specified.
rawNoWhether to return without compression (in PNG format). Default is false, which returns a JPEG image.
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.

Implementation Reference

  • Executes the screenshot logic: determines file type and name, configures Playwright screenshot options, handles element/fullPage/viewport screenshots using locators, saves to file, adds code and result to response, and adds image if not full page.
    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}`);
    
      // https://github.com/microsoft/playwright-mcp/issues/817
      // Never return large images to LLM, saving them to the file system is enough.
      if (!params.fullPage) {
        response.addImage({
          contentType: fileType === 'png' ? 'image/png' : 'image/jpeg',
          data: buffer
        });
      }
    }
  • Zod schema validating input parameters for browser_take_screenshot: type (png/jpeg), filename, element description, ref, fullPage boolean, with refinements ensuring element/ref pair or neither, and no fullPage with elements.
    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']
    });
  • Registers the browser_take_screenshot tool using defineTabTool, specifying name, title, description, input schema, and handler function. Exports it for inclusion in tools list.
    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}`);
    
        // https://github.com/microsoft/playwright-mcp/issues/817
        // Never return large images to LLM, saving them to the file system is enough.
        if (!params.fullPage) {
          response.addImage({
            contentType: fileType === 'png' ? 'image/png' : 'image/jpeg',
            data: buffer
          });
        }
      }
    });
    
    export default [
      screenshot,
    ];
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 useful context about the tool's limitations (no action capability) and distinguishes it from browser_snapshot, but doesn't provide additional behavioral details like rate limits, authentication needs, or what happens to the screenshot file after creation.

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 extremely concise with just two sentences, both of which earn their place by providing essential purpose clarification and usage guidance. No wasted words or redundant information.

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?

Given the tool's moderate complexity (screenshot capture with element targeting options), the description provides good purpose and usage context. With annotations covering safety aspects and no output schema, the main gap is lack of information about return values or what happens to the screenshot file, but the description adequately covers the core functionality.

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 fully documents all 4 parameters. 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'), and explicitly distinguishes it from the sibling tool 'browser_snapshot' by stating 'use browser_snapshot for actions'. This provides clear differentiation from alternatives.

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 provides explicit guidance on when NOT to use this tool ('You can't perform actions based on the screenshot') and names a specific alternative ('use browser_snapshot for actions'). This gives clear context for tool selection versus sibling 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

Related 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/JustasMonkev/mcp-accessibility-scanner'

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