Skip to main content
Glama
RonsDad
by RonsDad

browserbase_screenshot

Capture screenshots of web pages during browser automation to visually verify page states and locate elements when other methods are insufficient.

Instructions

Takes a screenshot of the current page. Use this tool to learn where you are on the page when controlling the browser with Stagehand. Only use this tool when the other tools are not sufficient to get the information you need.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe name of the screenshot

Implementation Reference

  • The main handler function for the browserbase_screenshot tool. It captures a screenshot of the current active Browserbase page, converts it to base64, stores it in the screenshots resource map, notifies the client of resource changes, and returns the screenshot as image content.
    async function handleScreenshot(
      context: Context,
      params: ScreenshotInput,
    ): Promise<ToolResult> {
      const action = async (): Promise<ToolActionResult> => {
        try {
          const page = await context.getActivePage();
          if (!page) {
            throw new Error("No active page available");
          }
    
          const screenshotBuffer = await page.screenshot({
            fullPage: false,
          });
    
          // Convert buffer to base64 string and store in memory
          const screenshotBase64 = screenshotBuffer.toString("base64");
          const name = params.name
            ? `screenshot-${params.name}-${new Date()
                .toISOString()
                .replace(/:/g, "-")}`
            : `screenshot-${new Date().toISOString().replace(/:/g, "-")}` +
              context.config.browserbaseProjectId;
          screenshots.set(name, screenshotBase64);
    
          // Notify the client that the resources changed
          const serverInstance = context.getServer();
    
          if (serverInstance) {
            serverInstance.notification({
              method: "notifications/resources/list_changed",
            });
          }
    
          return {
            content: [
              {
                type: "text",
                text: `Screenshot taken with name: ${name}`,
              },
              {
                type: "image",
                data: screenshotBase64,
                mimeType: "image/png",
              },
            ],
          };
        } catch (error) {
          const errorMsg = error instanceof Error ? error.message : String(error);
          throw new Error(`Failed to take screenshot: ${errorMsg}`);
        }
      };
    
      return {
        action,
        waitForNetwork: false,
      };
    }
  • The schema definition for the browserbase_screenshot tool, including name, description, and input schema (ScreenshotInputSchema defined above).
    const screenshotSchema: ToolSchema<typeof ScreenshotInputSchema> = {
      name: "browserbase_screenshot",
      description:
        "Takes a screenshot of the current page. Use this tool to learn where you are on the page when controlling the browser with Stagehand. Only use this tool when the other tools are not sufficient to get the information you need.",
      inputSchema: ScreenshotInputSchema,
    };
  • Local registration of the screenshot tool object, combining schema and handler, exported as default.
    const screenshotTool: Tool<typeof ScreenshotInputSchema> = {
      capability: "core",
      schema: screenshotSchema,
      handle: handleScreenshot,
    };
    
    export default screenshotTool;
  • Includes the screenshotTool in the main TOOLS array exported from tools/index.ts, which collects all available tools.
    export const TOOLS = [
      ...multiSessionTools,
      ...sessionTools,
      navigateTool,
      actTool,
      extractTool,
      observeTool,
      screenshotTool,
      getUrlTool,
    ];
  • src/index.ts:196-226 (registration)
    Registers all tools from TOOLS array with the MCP server using server.tool(), wrapping the tool handler with context.run(tool, params). This is where 'browserbase_screenshot' is registered in the MCP protocol.
    const tools: MCPToolsArray = [...TOOLS];
    
    // Register each tool with the Smithery server
    tools.forEach((tool) => {
      if (tool.schema.inputSchema instanceof z.ZodObject) {
        server.tool(
          tool.schema.name,
          tool.schema.description,
          tool.schema.inputSchema.shape,
          async (params: z.infer<typeof tool.schema.inputSchema>) => {
            try {
              const result = await context.run(tool, params);
              return result;
            } catch (error) {
              const errorMessage =
                error instanceof Error ? error.message : String(error);
              process.stderr.write(
                `[Smithery Error] ${new Date().toISOString()} Error running tool ${tool.schema.name}: ${errorMessage}\n`,
              );
              throw new Error(
                `Failed to run tool '${tool.schema.name}': ${errorMessage}`,
              );
            }
          },
        );
      } else {
        console.warn(
          `Tool "${tool.schema.name}" has an input schema that is not a ZodObject. Schema type: ${tool.schema.inputSchema.constructor.name}`,
        );
      }
    });
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool helps 'learn where you are on the page' which provides useful context about its purpose, but doesn't disclose important behavioral aspects like whether this is a read-only operation, what format the screenshot returns, or any performance implications. The description adds some value but leaves significant gaps.

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 three sentences that each serve distinct purposes: stating the action, providing usage context, and giving exclusion criteria. Every sentence earns its place with no wasted words, and the information is front-loaded with the core functionality stated first.

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 relative simplicity (single optional parameter, no output schema, no annotations), the description provides good context about when and why to use it. However, it doesn't explain what the tool returns (screenshot format or location) or address potential limitations. For a screenshot tool with no output schema, this represents a minor gap in completeness.

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

Parameters4/5

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

With 100% schema description coverage and only one optional parameter ('name'), the schema already fully documents the parameter. The description doesn't add any parameter-specific information, but with minimal parameters and complete schema coverage, this is acceptable. The baseline would be 3, but the description's focus on usage context rather than parameters justifies a slightly higher score.

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 ('Takes a screenshot') and resource ('current page'), distinguishing it from sibling tools like navigation or extraction tools. It provides a precise verb+resource combination that leaves no ambiguity about what the tool does.

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 states when to use this tool ('when controlling the browser with Stagehand' and 'when the other tools are not sufficient to get the information you need') and provides clear alternatives by referencing 'other tools' in the context of sibling Stagehand tools. This gives the agent specific guidance on appropriate usage scenarios.

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/RonsDad/mcp-server-browserbase'

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