Skip to main content
Glama

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 core handler function that executes the screenshot logic: determines file type, generates locator if element specified, prepares code snippet, defines an action to capture the screenshot using Playwright, and returns base64 image if supported.
    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,
      };
    }
  • Zod schema for input parameters validation of the browser_take_screenshot tool.
    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']
    });
  • Tool schema definition including name, title, description, inputSchema reference, and type.
    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',
    },
  • Export of the defined screenshot tool for inclusion in tools arrays.
    export default [
      screenshot,
    ];
  • src/tools.ts:35-50 (registration)
    Inclusion of the screenshot tool (via ...screenshot) into the snapshotTools array, which registers it for use.
    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 and destructiveHint=false, establishing this as a safe read operation. The description adds some behavioral context about the inability to perform actions on screenshots, but doesn't provide additional behavioral details like rate limits, file storage behavior, or error conditions that would be valuable beyond the annotations.

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 perfectly concise with only two sentences that both earn their place. The first sentence states the core purpose, and the second provides crucial usage guidance. There's zero wasted text or redundancy.

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 (100% schema coverage) and clear annotations, the description provides adequate context. It explains the core purpose and key usage distinction. The main gap is the lack of output information (no output schema), but the description compensates reasonably well given the tool's relative simplicity.

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 thoroughly documents all 5 parameters. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline expectation but doesn't provide additional semantic context.

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 ('of the 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 and 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/manishamishraacc/mcp'

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