Skip to main content
Glama

read_page

Read-onlyIdempotent

Extract page content as DOM, accessibility tree, CSS diagnostics, semantic summary, or clean Markdown. Use for reading structure, verifying content, or extracting articles.

Instructions

Get page as DOM, accessibility tree (ax), CSS diagnostics, semantic summary, or clean Markdown (article-shaped).

When to use: Reading page structure, verifying content, extracting the full DOM tree, or reducing article-like pages to Markdown. When NOT to use: Use inspect for targeted state queries or find to locate a specific element.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdNoTab ID to read from
taskIdNoTask id when using a task-scoped browser lane.
laneIdNoTask-scoped browser lane id; validates tabId or defaults to the lane current target.
depthNoMax tree depth. Default: 8 (all), 5 (interactive)
filterNoFilter: interactive for form/button/link only
ref_idNoParent ref for subtree scoping
selectorNoCSS selector (css mode only)
modeNoOutput mode: dom (default), ax, css, semantic, or markdown (clean article extraction).
onlyMainContentNoMarkdown mode only: strip nav/header/footer/aside/ads. Default: true.
includeLinksNoMarkdown mode only: preserve <a> as markdown links. Default: true.
contentFilterNoMarkdown mode only: deterministic fit_markdown filter. Default: none.
queryNoMarkdown mode only: required when contentFilter="bm25".
returnRawNoMarkdown mode only: include raw_markdown in JSON response. Default: false.
returnFitNoMarkdown mode only: include fit_markdown and use it as content when filtering. Default: true when filtered.
filterOptionsNoMarkdown mode only: minWords, maxSections, bm25Threshold, pruneThreshold.
includePaginationNoInclude pagination info. Default: true
cursorNoMarkdown mode only: opaque cursor returned as nextCursor from a prior paginated read_page markdown call.
compressionNoCompression mode. "delta" returns only changes since last read.
planningProfileNoDOM mode only: stable omits decorative/noisy serialization details without mutating the live page. Default: default.
fallbackNoAX mode only: use "dom" to explicitly fall back to DOM output if AX output exceeds the output budget. Default: none.
compactNoAX mode only: return a compact AX snapshot that keeps actionable/ref-bearing nodes, value/state nodes, and ancestors. Default: false, or true when OPENCHROME_PROFILE=fast.
diagnosticsNoInclude structured read_page timing diagnostics in the MCP result metadata. Default: false.
include_metricsNoWhen true, include approximate returned size/token metrics in the emitted payload. Default: false.
boundaryMarkersNoWrap page-origin plaintext in <oc:page>. Default true; false disables.
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds context about output modes, compression, fallback, and planning profiles, but doesn't reveal significant behavioral traits beyond what annotations imply. No contradictions.

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?

Description is front-loaded with purpose, followed by concise usage guidelines. Slightly longer due to multiple modes, but well-structured and each sentence earns its place.

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 complexity (24 params, no output schema), the description provides sufficient context for agent decision-making, covering usage, alternatives, and key behaviors. Minor gaps like return structure could be inferred.

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?

All 24 parameters are fully described in the schema (100% coverage), so the description adds minimal extra meaning. Baseline 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 it retrieves page content in multiple formats (DOM, AX, CSS, semantic, markdown) and explicitly distinguishes from sibling tools inspect and find in the 'When NOT to use' section.

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 'When to use' and 'When NOT to use' sections, naming alternatives and scenarios, which is ideal for guiding an agent's decision.

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/shaun0927/openchrome'

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