Skip to main content
Glama
VikashLoomba

MCP-Server-Playwright

browser_screenshot

Capture web page screenshots or specific elements using CSS selectors for documentation, testing, or visual verification in browser automation workflows.

Instructions

Take a screenshot of the current page or a specific element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the screenshot
selectorNoCSS selector for element to screenshot
fullPageNoTake a full page screenshot (default: false)

Implementation Reference

  • Handler function for the 'browser_screenshot' tool. Captures screenshot of page or element using Playwright, converts to base64, stores it, notifies resource change, and returns success message with image content.
    case ToolName.BrowserScreenshot: {
      const fullPage = (args.fullPage === 'true');
    
      const screenshot = await (args.selector ?
        page.locator(args.selector).screenshot() :
        page.screenshot({ fullPage }));
      const base64Screenshot = screenshot.toString('base64');
    
      if (!base64Screenshot) {
        return {
          content: [{
            type: "text",
            text: args.selector ? `Element not found: ${args.selector}` : "Screenshot failed",
          }],
          isError: true,
        };
      }
    
      screenshots.set(args.name, base64Screenshot);
      server.notification({
        method: "notifications/resources/list_changed",
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Screenshot '${args.name}' taken`,
          } as TextContent,
          {
            type: "image",
              data: base64Screenshot,
              mimeType: "image/png",
            } as ImageContent,
          ],
        isError: false,
      };
    }
  • index.ts:48-60 (registration)
    Tool registration object for 'browser_screenshot' added to the TOOLS array, which is served via ListToolsRequestSchema. Includes name, description, and input schema.
    {
      name: ToolName.BrowserScreenshot,
      description: "Take a screenshot of the current page or a specific element",
      inputSchema: {
        type: "object",
        properties: {
          name: { type: "string", description: "Name for the screenshot" },
          selector: { type: "string", description: "CSS selector for element to screenshot" },
          fullPage: { type: "boolean", description: "Take a full page screenshot (default: false)", default: false },
        },
        required: ["name"],
      },
    },
  • Input schema defining parameters for browser_screenshot: name (required), selector (optional), fullPage (optional boolean).
    inputSchema: {
      type: "object",
      properties: {
        name: { type: "string", description: "Name for the screenshot" },
        selector: { type: "string", description: "CSS selector for element to screenshot" },
        fullPage: { type: "boolean", description: "Take a full page screenshot (default: false)", default: false },
      },
      required: ["name"],
    },
  • Enum definition mapping ToolName.BrowserScreenshot to the string 'browser_screenshot' used throughout the code.
    BrowserScreenshot = "browser_screenshot",
  • index.ts:640-646 (registration)
    MCP server request handlers for listing tools (via TOOLS array) and calling tools (routes to handleToolCall switch).
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
    
    server.setRequestHandler(CallToolRequestSchema, async (request) =>
      handleToolCall(request.params.name as ToolName, request.params.arguments ?? {})
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but provides minimal information. It mentions what the tool does but doesn't describe important behavioral aspects: whether this captures the current browser state, what format the screenshot returns, whether it saves to disk or returns binary data, or any performance implications. For a tool with visual output and potential resource usage, this is inadequate.

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 a single, efficient sentence that communicates the core functionality without unnecessary words. It's appropriately sized for a straightforward tool and front-loads the essential information. Every word earns its place in this compact description.

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?

Given that this is a visual capture tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what format the screenshot returns (image data, file path, base64), whether it captures the current viewport or can scroll, or how it handles dynamic content. For a tool that produces visual output, more context about the result is needed.

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%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it mentions 'current page or a specific element' which aligns with the selector parameter but doesn't provide extra context about parameter interactions or usage patterns.

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 clearly states the action ('Take a screenshot') and target ('current page or a specific element'), making the purpose immediately understandable. It distinguishes from siblings by focusing on screenshot capture rather than navigation, interaction, or evaluation. However, it doesn't explicitly differentiate from potential screenshot alternatives that might exist in other contexts.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention whether this is for debugging, documentation, or visual verification, nor does it suggest when to use element-specific versus full-page screenshots. With multiple browser interaction siblings available, the lack of contextual guidance is a significant gap.

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/VikashLoomba/MCP-Server-Playwright'

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