Skip to main content
Glama

browser_snapshot

Capture webpage snapshots using a managed browser pool to resolve session conflicts and enable concurrent, isolated browsing sessions.

Instructions

Page snapshot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • index.js:317-330 (registration)
    The browser_snapshot tool is registered here and delegates the execution to proxyToolCall.
    server.tool('browser_snapshot', 'Page snapshot', {},
      async () => {
        log(`[browser_snapshot] called`);
        const check = requireActivePage();
        if (check) return check;
        try {
          const result = await proxyToolCall('browser_snapshot', {});
          log(`[browser_snapshot] result: ${JSON.stringify(result).slice(0, 500)}`);
          return result;
        } catch (err) {
          log(`[browser_snapshot] ERROR: ${err.message}\n${err.stack}`);
          throw err;
        }
      });
Behavior1/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, yet reveals nothing about return format, potential errors, timeouts, or whether the snapshot includes iframes/visibility states. The agent cannot predict what data structure it receives.

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

Conciseness2/5

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

While only two words, this represents under-specification rather than efficient conciseness. The single 'sentence' fails to earn its place by providing actionable information about the tool's behavior or output.

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 lack of output schema and annotations, the description needed to compensate by explaining what the snapshot contains (HTML, text, accessibility tree). It provides none of this, leaving critical gaps for a tool that presumably returns complex page data.

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?

The input schema has zero parameters, which establishes a baseline score of 4. The description appropriately indicates no inputs are needed, though it doesn't explicitly confirm this (but none was expected given the empty schema).

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 'Page snapshot' is essentially a tautology that restates the tool name without clarifying what kind of snapshot (DOM, text, image?) or what it returns. While it implies a read operation on a page, it fails to distinguish from sibling tools like browser_screenshot or browser_navigate.

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?

No guidance provided on when to use this tool versus alternatives like browser_screenshot (likely for images) or browser_evaluate (for scripted extraction). No mention of prerequisites like needing an active navigation session.

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