Skip to main content
Glama

Read the page

browser_read
Destructive

The current page's text as Markdown (or plain text), read from the live page by the same reader as the Extract API, with the page's URL and the time of the read. Takes the session_id from open_browser. 0.1¢ a step that runs.

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
formatNomarkdown (the default) or text.markdown
session_idYesThe session id open_browser returned.

Output Schema

NameRequiredDescriptionDefault
urlNoThe address of the page after the step.
errorNoWhy the step failed, when it failed.
titleNoThe page title.
read_atNoWhen the page was read.
took_msNoHow long the step took.
price_usdNoWhat the step cost, in dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "The page after the step, and what the step cost.",
      +  "properties": {
      +    "error": {
      +      "description": "Why the step failed, when it failed.",
      +      "type": "object"
      +    },
      +    "price_usd": {
      +      "description": "What the step cost, in dollars.",
      +      "type": "number"
      +    },
      +    "read_at": {
      +      "description": "When the page was read.",
      +      "type": "string"
      +    },
      +    "title": {
      +      "description": "The page title.",
      +      "type": "string"
      +    },
      +    "took_ms": {
      +      "description": "How long the step took.",
      +      "type": "integer"
      +    },
      +    "url": {
      +      "description": "The address of the page after the step.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / format / description
      Added value: +"markdown (the default) or text."
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

The description contributes real information beyond the annotations: a per-step cost of 0.1¢ that runs, the reader's identity matching the Extract API, and the returned URL/timestamp. However, the annotations declare readOnlyHint=false and destructiveHint=true for what reads as a passive read, and the description says nothing about side effects, session state changes, or whether long pages are truncated — a notable gap for a tool flagged destructive.

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?

Two sentences, front-loaded with the result and followed by the requirement and pricing; nothing is padded. The first sentence is a long fragment that stacks several clauses, which slightly hurts scanability but not substance.

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

Completeness3/5

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

With an output schema present, the description needn't document return values, and the cost and prerequisite are covered. For a live-page reader with openWorld and destructive flags, it should still address truncation/large-page behavior and why the call is marked destructive.

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 description coverage is 100%, with both session_id and the format enum already documented in the schema, so the baseline of 3 applies. The description's mention of session_id coming from open_browser restates the schema rather than adding new semantics such as format trade-offs or size limits.

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 names the resource (the current page) and the result (its text as Markdown or plain text), plus what accompanies it (the page URL and read timestamp), so an agent knows exactly what this returns. It does not distinguish itself from sibling read paths like browser_snapshot or read_pages, leaving that differentiation to inference.

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

Usage Guidelines3/5

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

It gives one concrete prerequisite: 'Takes the session_id from open_browser', which tells the agent the required ordering. It offers only oblique positioning against alternatives ('the same reader as the Extract API'), and never states when to prefer this over browser_snapshot or browser_find, or when it should not be used.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.