Skip to main content
Glama

read_page

Extract a page's visible text and interactive elements with refs for clicking, typing, selecting, and checking states; use these refs to drive browser controls.

Instructions

Outline of the page's visible interactive elements and text.

Interactive elements get refs like r12 for click and type. Checkboxes, radios and
switches show checked or unchecked. "clickable" marks an element with a pointer
cursor but no role, often a custom toggle; its label is usually the text before it.
An open dropdown's options are listed under it, the first few only; select picks any.
Refs expire when you call read_page again or the page navigates. Refs that click, type
and select give for new controls count as this read_page's.

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
tab_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does an unusually good job: it discloses ref expiry rules, that dropdown options are truncated to the first few (select can still reach any), how checked state and 'clickable' custom toggles are represented, and that newly created controls count against the current read. Gaps: nothing about which tab is read by default, response size limits, or permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the return semantics, which is correct, and has little padding. But the final sentence ('Refs that click, type and select give for new controls count as this read_page's') is garbled and hard to parse, and the dropdown/clickable notes are ordered awkwardly.

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 no output schema and no annotations, the description must explain the return shape, and it largely does—element outline, ref format, state markers, truncation. The missing piece is tab targeting: the only parameter's default behavior is undocumented, leaving an ambiguity an agent will hit immediately with multiple tabs open.

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

Parameters2/5

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

The single parameter tab_id has 0% schema description coverage, and the description never mentions it. An agent cannot tell from either source whether omitting tab_id reads the active tab or defaults to something else, which matters in a multi-tab workflow with list_tabs/switch_tab siblings.

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 makes clear what the tool returns: an outline of visible interactive elements plus text, with refs (r12) used by click, type and select. That implicitly separates it from the action siblings. It does not, however, distinguish it from get_text, which is the nearest ambiguous sibling for 'read page content'.

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?

Usage is only implied: refs come from this tool and expire when you call it again or navigate, so an agent can infer it must call read_page before click/type/select. There is no explicit when-to-use statement and no exclusion or comparison against get_text or screenshot.

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