Skip to main content
Glama

Read the page's text

browser_read
Read-only

Reads the current page as rendered text or live HTML from an open browser session, returning structured extract-shaped content you can inspect or fetch in full via its handle.

Instructions

Read the page as it is now, as text or live HTML, shaped like an extract result; fetch_raw with its handle returns all of it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "browser_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo'text', the rendered text of the page, or 'html', the live DOM. Unset, 'text'.
timeoutNoSeconds; unset, 30.
session_idYesThe session_id `browser_open` returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.14.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavior beyond that: the content reflects the live current DOM, and the result may be bounded ('shaped like an extract result') with `fetch_raw` needed for the full payload, implying possible truncation.

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?

A single dense sentence with the core scope front-loaded and the alternative appended. No filler, though the backticked references make it read slightly like shorthand rather than a standalone explanation.

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?

For a 3-parameter read tool with no output schema and clear annotations, the definition covers what the call does, the return-mode choice, and where to go for full content. The only gap is not distinguishing itself from snapshot/extract style siblings.

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%, so format, timeout, and session_id are already fully documented in the schema. The description's 'text or live HTML' merely restates the format enum without adding syntax or edge-case detail, so it sits at the baseline.

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?

States a specific verb and resource ('Read the page') with the important qualifier 'as it is now', and names the two output modes (text or live HTML). The comparison to an `extract` result shape and to `fetch_raw` gives the agent a concrete mental model, though the phrasing is somewhat terse.

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

Usage Guidelines4/5

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

The phrase 'as it is now' signals this should be called after the page is in the desired state, and it explicitly routes the agent to `fetch_raw` when the complete content is needed. It does not spell out when not to use it versus `browser_snapshot` or `extract`, but the primary alternative is named.

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