Skip to main content
Glama

browser_screenshot

Capture screenshots from web browsers using Playwright sessions. Manage multiple concurrent instances with automatic cleanup for efficient browser automation.

Instructions

Take screenshot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullPageNo

Implementation Reference

  • index.js:352-358 (registration)
    Registration of the 'browser_screenshot' tool. It validates input via zod schema and then calls 'proxyToolCall' with the actual tool name 'browser_take_screenshot'.
    server.tool('browser_screenshot', 'Take screenshot', {
      fullPage: z.boolean().optional()
    }, async (args) => {
      const check = requireActivePage();
      if (check) return check;
      return proxyToolCall('browser_take_screenshot', args);
    });
  • The 'proxyToolCall' function acts as a wrapper that forwards tool requests to an external client instance. This handles the actual execution logic for tools like 'browser_take_screenshot'.
    async function proxyToolCall(toolName, args) {
      log(`[proxyToolCall] ${toolName} with args: ${JSON.stringify(args)}`);
      const { client } = await getOrCreateInstance();
      log(`[proxyToolCall] got client for port ${assignedPort}`);
    
      // Update last used
      if (assignedPort && instances.has(assignedPort)) {
        instances.get(assignedPort).lastUsed = Date.now();
      }
    
      try {
        log(`[proxyToolCall] Calling client.callTool...`);
        const result = await client.callTool({ name: toolName, arguments: args || {} });
        log(`[proxyToolCall] Result type: ${typeof result}`);
        log(`[proxyToolCall] Result: ${JSON.stringify(result).slice(0, 500)}`);
    
        // The SDK returns { content: [...], isError?: boolean }
        // We need to return this same format
        if (result && result.content) {
          return result;
        }
    
        // Fallback: wrap in content array if needed
        return {
          content: [{ type: 'text', text: JSON.stringify(result) }]
        };
      } catch (error) {
        log(`[proxyToolCall] ERROR: ${error.message}\n${error.stack}`);
        return {
Behavior2/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 only indicates a capture action but lacks critical context: output format (PNG? JPEG?), return type (file path? base64? binary?), viewport handling, and whether the operation blocks until page is stable.

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

Conciseness3/5

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

Extremely brief at two words, but this crosses into under-specification rather than efficient conciseness. The single 'sentence' does not earn its place by providing actionable guidance beyond the tool name itself.

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?

Inadequate for a tool with 1 undocumented parameter and a confusingly similar sibling (browser_snapshot). Without output schema or annotations, the description should at minimum clarify the capture scope and differentiate from snapshot functionality.

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?

Schema coverage is 0% for the fullPage boolean parameter, and the description fails to compensate by explaining what fullPage controls (full page vs viewport capture) or when an agent should set it to true.

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

Purpose2/5

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

The description 'Take screenshot' is a tautology that merely restates the tool name (browser_screenshot → 'Take screenshot'). It fails to distinguish from sibling tool browser_snapshot, leaving ambiguity about whether this captures the visible viewport, full DOM, or static image.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., browser_snapshot), when to set fullPage=true vs false, or prerequisites such as requiring an open browser context.

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/OMGEverdo/browser-pool-mcp'

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