Hercules MCP

Overview Schema Source Related Servers Discussions Admin

browser_snapshot

Capture a page's accessibility tree as compact text with stable element references. Use options to trim or expand details for targeted analysis.

Instructions

Purpose: Capture the page's accessibility tree as compact text with stable element references (@e1, @e2, ...).… Constraints: compact is default; detailed requests an uncompacted unlimited-depth tree. Use interactive, include_urls, depth, or selector to narrow/expand it. Iframes auto-inline… Example: browser_snapshot(session='recon')

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_snapshot"
  }
}

Input Schema

Name	Required	Default
`depth`	No
`compact`	No
`session`	No	default
`detailed`	No
`selector`	No
`interactive`	No
`include_urls`	No
`inline_iframes`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses compact vs detailed output, iframe inlining, and stable references, but does not explicitly mention side effects or permissions. Still, it adds meaningful behavioral context.

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

Conciseness4/5

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

The description is structured with clear sections (Purpose, Constraints, Example) and is concise. It front-loads the core purpose and uses compact phrasing, though the ellipsis suggests possible truncation.

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 8 optional parameters and output schema, the description covers most functionality, including narrowing/expanding options. However, it omits a full explanation of the session parameter and lacks alternative tool guidance, leaving some gaps.

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 description explains the effects of compact, detailed, interactive, include_urls, depth, selector, and implies inline_iframes. Session is shown in the example but not explicitly described. Since schema coverage is 0%, this compensation is valuable.

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 tool captures the page's accessibility tree as compact text with stable element references, using a specific verb and resource. It distinguishes itself from sibling browser tools by focusing on the accessibility tree and element references.

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

Usage Guidelines3/5

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

The description provides parameter constraints but does not explicitly compare with alternatives or state when to use this tool versus siblings. It implies usage for capturing snapshots, but lacks exclusionary guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.