AIHawk

Official

Overview Schema Source Related Servers Discussions Admin

browser_read_html

Extract cleaned page HTML to inspect structure, such as forms, labels, tables, and control wiring, when relationships in the markup matter. Returns the full reduced page without truncation.

Instructions

The page's HTML, cleaned down to what is worth reading.

Use this when the STRUCTURE matters - a form and its labels, a table, what a control is wired to. browser_snapshot gives a flat inventory of things to click; this keeps the markup and the relationships inside it.

mode="form" keeps the interactive surface and the text explaining it, mode="text" returns the prose alone, mode="full" keeps the structure with the noise and the attribute soup removed.

Unlike browser_read_text this is NOT capped: it returns the whole reduced page, tens of thousands of characters on a large one. Cutting markup in the middle leaves tags that mean nothing, so it is not cut - but the answer can be long. Reach for browser_snapshot when you only need something to click.

browser is main unless you say support, and they share nothing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No		form
`browser`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.43.0Sep 12, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the critical trait that output is NOT capped and can be 'tens of thousands of characters', explains why it is not truncated (broken tags), and warns that `main` and `support` browsers 'share nothing'. These are exactly the behaviors an agent needs before invoking.

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?

Front-loads the identity of the tool in the first line, then adds modes, then size caveat, then routing. Dense but every sentence carries distinct decision-relevant information; no filler.

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

Completeness5/5

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

An output schema exists, so return values need not be described. For a 2-param, zero-required read tool, the description covers purpose, mode semantics, browser context isolation, output size expectations, and sibling routing - nothing material is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate and does: it defines all three `mode` values (form = interactive surface plus explanatory text, text = prose alone, full = structure minus attribute soup) and clarifies `browser` defaults to main and that the two browsers are isolated. This is meaning the schema does not provide.

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?

States a specific verb and resource ('the page's HTML, cleaned down to what is worth reading') and immediately frames the differentiator: structure preservation versus browser_snapshot's flat clickable inventory. An agent can distinguish this from browser_read_text and browser_snapshot without opening any schema.

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?

Gives an explicit selection rule ('Use this when the STRUCTURE matters - a form and its labels, a table, what a control is wired to') and names the alternatives with their selecting conditions: browser_snapshot 'when you only need something to click', and a direct contrast with browser_read_text on capping.

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

Deploy Server