Skip to main content
Glama
Sign In
Chrome Bridge

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

read_page

Read-onlyIdempotent

Extract page content from the current tab in text, markdown, HTML, or accessibility formats. Optionally save the output to a file.

Instructions

Read the page as text (default), markdown, raw HTML, or accessibility tree. Read-only. markdown keeps headings, links and tables at a fraction of the HTML cost. Expensive on big pages: HTML on a large table costs tens of thousands of tokens for data you filter anyway — prefer extract_table/extract for repeated content, get_interactives for click targets.

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": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNotext strips markup; markdown keeps headings/links/tables far cheaper than html; accessibility = a11y treetext
tab_idNoTarget tab; omitted = last tab navigated in this session, else the active one
save_toNoAbsolute path: write the page there and return the path instead of the content
frame_idNoTarget iframe id from get_frames; omitted = main frame
max_lengthNoMax output chars

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.1
    • changedInput schema / properties / mode / description
      Previous value: -"text strips markup, markdown keeps headings/links/tables far cheaper than html, accessibility returns the a11y tree"New value: +"text strips markup; markdown keeps headings/links/tables far cheaper than html; accessibility = a11y tree"
  2. Changed3 schema fields changedv1.11.0
    • changedInput schema / properties / mode / description
      Previous value: -"text strips markup, html keeps it (costly), accessibility returns the a11y tree"New value: +"text strips markup, markdown keeps headings/links/tables far cheaper than html, accessibility returns the a11y tree"
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "text",
-  "html",
-  "accessibility"
-]New value: +[
+  "text",
+  "markdown",
+  "html",
+  "accessibility"
+]
    • addedInput schema / properties / save_to
      Added value: +{
+  "description": "Absolute path: write the page there and return the path instead of the content",
+  "type": "string"
+}
  3. Changed3 schema fields changedv1.10.0
    • addedInput schema / properties / frame_id / description
      Added value: +"Target iframe id from get_frames; omitted = main frame"
    • addedInput schema / properties / mode / description
      Added value: +"text strips markup, html keeps it (costly), accessibility returns the a11y tree"
    • addedInput schema / properties / tab_id / description
      Added value: +"Target tab; omitted = last tab navigated in this session, else the active one"
  4. First observedv1.8.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses that the operation is read-only and that HTML mode can be token-expensive, adding useful behavioral context about resource usage.

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 well-structured and front-loaded with the purpose, but includes some redundancy around HTML cost and repeated mentions of the same idea, so it is slightly less concise than ideal.

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?

Provides sufficient context for selecting and using the tool, including cost implications and alternatives, though it does not cover potential output variations or errors beyond what the schema implies.

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?

The schema already provides 100% parameter description coverage with clear details for each param, so the tool description adds no extra parameter semantics; baseline of 3 is appropriate.

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 reads a page in multiple modes (text, markdown, HTML, accessibility tree) and distinguishes it from siblings by advising when to use extract_table or get_interactives instead.

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?

Provides explicit usage guidance: warns about high token costs on big pages and recommends alternative tools for repeated content or click targets, making the when-to-use decision clear.

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