Skip to main content
Glama
epi-builder
by epi-builder

browser_snapshot

Capture accessibility snapshots of web pages to analyze structure and identify potential issues for improved user experience.

Instructions

Capture accessibility snapshot of the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the 'browser_snapshot' tool. It ensures the browser and page are initialized, retrieves the current page's title and URL, and returns a textual snapshot response.
      private async handleSnapshot() {
        await this.ensureBrowser();
        
        // Get page content and create a simple snapshot
        const title = await this.browserState.page!.title();
        const url = this.browserState.page!.url();
        
        return {
          content: [
            {
              type: 'text',
              text: `Page Snapshot:
    Title: ${title}
    URL: ${url}
    [Use browser_click, browser_type tools to interact with elements]`,
            },
          ],
        };
      }
  • Input schema for the 'browser_snapshot' tool, defining an empty object (no required parameters).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • src/server.ts:74-81 (registration)
    Registration entry for the 'browser_snapshot' tool in the ListToolsRequestSchema response, including name, description, and input schema.
    {
      name: 'browser_snapshot',
      description: 'Capture accessibility snapshot of the current page',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/server.ts:160-161 (registration)
    Dispatch registration in the CallToolRequestSchema switch statement, routing calls to the handleSnapshot() function.
    case 'browser_snapshot':
      return await this.handleSnapshot();
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 states the action ('capture') but doesn't clarify whether this is a read-only operation, what format the snapshot returns, if it requires specific permissions, or if it has side effects. For a tool with zero annotation coverage, this leaves significant behavioral 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 a single, efficient sentence that directly states the tool's purpose without any fluff. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, and there's no wasted verbiage.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate as a minimum viable explanation. However, it lacks details about the output format, behavioral traits, and usage context, which would be helpful for an AI agent. The description meets basic needs but has clear gaps 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?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, which is correct for a parameterless tool. A baseline of 4 is applied since the description doesn't need to compensate for any parameter gaps.

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 ('capture') and the resource ('accessibility snapshot of the current page'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'browser_take_screenshot', but the specific focus on 'accessibility' provides some implicit distinction. A perfect 5 would require 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 like 'browser_take_screenshot' or other browser tools. It doesn't mention prerequisites (e.g., needing an active browser page) or contextual constraints. The description merely states what it does without indicating 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/epi-builder/mcp-test'

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