Skip to main content
Glama
Sign In
browser-mcp-cdp

browser-mcp-cdp

by zhiqi-li
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_get_html

Retrieve the outer HTML of a webpage or a specific element using a CSS selector. Get the full page markup or a targeted element's HTML.

Instructions

Get the outer HTML of the page or a specific element.

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_get_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorNoCSS selector (optional, defaults to full page HTML)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must disclose behavior. It reveals it gets outer HTML but omits error conditions (e.g., selector not found), potential size warnings, or whether it blocks. This is adequate but has 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?

A single sentence of 12 words conveys purpose and parameter option. No unnecessary words, and the structure is efficient.

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?

No output schema exists, so the description should clarify the return type (string) and format. It does not mention what HTML is returned (e.g., escaped? full document? ) nor contrasts with sibling tools. Incomplete for a read tool.

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

Parameters3/5

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

Schema coverage is 100%. The description repeats that 'selector' is optional and defaults to full page HTML, adding no extra meaning beyond the schema. Baseline 3 applies.

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 it retrieves the outer HTML of the page or a specific element using a CSS selector. This distinguishes it from sibling tools like 'browser_get_text' (text content) and 'browser_get_url' (URL), though it does not explicitly differentiate them.

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?

No guidance is provided on when to use this tool vs alternatives like 'browser_get_text' or 'browser_evaluate'. There are no when-not scenarios or prerequisites mentioned, leaving the agent to infer usage.

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

Deploy Server

Other Tools