Skip to main content
Glama

screenshot

Capture browser screenshots in PNG or JPEG format, including full-page scrolling captures, for documentation, testing, or visual analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoImage format
fullPageNoCapture full scrollable page

Implementation Reference

  • server.js:69-81 (handler)
    Handler function that launches a browser if needed, takes a screenshot using Playwright's page.screenshot with specified format and fullPage options, converts to base64, and returns as image content.
    async ({ format = "png", fullPage = false }) => {
      const { page } = await ensureBrowser();
      const buffer = await page.screenshot({ type: format, fullPage });
      return {
        content: [
          {
            type: "image",
            data: buffer.toString("base64"),
            mimeType: `image/${format}`,
          },
        ],
      };
    }
  • Input schema using Zod for the screenshot tool parameters: optional format (png or jpeg) and fullPage boolean.
    {
      format: z.enum(["png", "jpeg"]).optional().describe("Image format"),
      fullPage: z.boolean().optional().describe("Capture full scrollable page"),
    },
  • server.js:62-82 (registration)
    Registration of the 'screenshot' tool using McpServer.tool, including schema and inline handler.
    // Convenience: Take screenshot (returns base64 image)
    server.tool(
      "screenshot",
      {
        format: z.enum(["png", "jpeg"]).optional().describe("Image format"),
        fullPage: z.boolean().optional().describe("Capture full scrollable page"),
      },
      async ({ format = "png", fullPage = false }) => {
        const { page } = await ensureBrowser();
        const buffer = await page.screenshot({ type: format, fullPage });
        return {
          content: [
            {
              type: "image",
              data: buffer.toString("base64"),
              mimeType: `image/${format}`,
            },
          ],
        };
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/Myestery/browser-cdp-mcp'

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