Skip to main content
Glama
cploujoux

Puppeteer MCP Server

by cploujoux

puppeteer_screenshot

Capture webpage or element screenshots with customizable dimensions using CSS selectors, enabling precise visual extraction for browser automation tasks.

Instructions

Take a screenshot of the current page or a specific element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
heightNoHeight in pixels (default: 600)
nameYesName for the screenshot
selectorNoCSS selector for element to screenshot
widthNoWidth in pixels (default: 800)

Implementation Reference

  • Handler for puppeteer_screenshot tool: sets viewport, captures screenshot of page or specified element, stores it in screenshots map, notifies resource change, returns success message and image content or error if failed.
    case "puppeteer_screenshot": {
      const width = args.width ?? 800;
      const height = args.height ?? 600;
      await page.setViewport({ width, height });
    
      const screenshot = await (args.selector
        ? (await page.$(args.selector))?.screenshot({ encoding: "base64" })
        : page.screenshot({ encoding: "base64", fullPage: false }));
    
      if (!screenshot) {
        return {
          content: [
            {
              type: "text",
              text: args.selector
                ? `Element not found: ${args.selector}`
                : "Screenshot failed",
            },
          ],
          isError: true,
        };
      }
    
      screenshots.set(args.name, screenshot as string);
      server.notification({
        method: "notifications/resources/list_changed",
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Screenshot '${args.name}' taken at ${width}x${height}`,
          } as TextContent,
          {
            type: "image",
            data: screenshot,
            mimeType: "image/png",
          } as ImageContent,
        ],
        isError: false,
      };
    }
  • Input schema definition for puppeteer_screenshot tool within the TOOLS array, specifying required 'name' and optional 'selector', 'width', 'height' parameters.
    {
      name: "puppeteer_screenshot",
      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",
          },
          width: {
            type: "number",
            description: "Width in pixels (default: 800)",
          },
          height: {
            type: "number",
            description: "Height in pixels (default: 600)",
          },
        },
        required: ["name"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Take a screenshot') but doesn't describe what happens after (e.g., returns an image file, saves locally, requires permissions, or has rate limits). For a tool with potential side effects (like file creation) and no annotations, this is a significant gap, warranting a score of 2.

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 directly states the tool's purpose without any fluff or redundancy. It's front-loaded and every word earns its place, making it highly concise and well-structured, deserving a score of 5.

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 the complexity (a screenshot tool with potential behavioral implications), lack of annotations, and no output schema, the description is incomplete. It doesn't cover return values (e.g., image data or file path), error conditions, or dependencies on other tools like puppeteer_navigate. This leaves significant gaps for an AI agent to use it effectively, resulting in a score of 2.

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?

The input schema has 100% description coverage, with clear documentation for all 4 parameters (height, name, selector, width), including defaults. The description adds no additional parameter semantics beyond what the schema provides, such as explaining how 'selector' interacts with 'current page' or format details. With high schema coverage, the baseline is 3, which is appropriate here.

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 the target ('current page or a specific element'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like puppeteer_click or puppeteer_navigate, though the verb 'screenshot' inherently distinguishes it. This earns a 4 for clear purpose without explicit sibling differentiation.

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 prerequisites (e.g., needing a page loaded via puppeteer_navigate first), exclusions, or comparisons to other screenshot-related tools if any existed. This lack of contextual usage information results in a score of 2.

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/cploujoux/mcp-puppeteer'

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