Skip to main content
Glama

read_page

Returns a structured outline of a tab's page elements with roles, names, and ref IDs for clicking, typing, or filling forms; filter interactive controls or include headings, text, and images.

Instructions

Get a structured outline of the page: elements with their role, name and a ref ID to use with click/type/form_input. filter "interactive" (default) lists only buttons, links and inputs; "all" also includes headings, text and images.

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": {
      "tabId": "<tabId>"
    },
    "name": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoOnly outline the subtree under this element
tabIdYesTab ID, from tabs_list or tab_create
filterNo
maxCharsNoOutput cap, default 40000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does explain output shape and filter behavior, but omits whether refs go stale after navigation or DOM changes, whether the page must be loaded first, and how maxChars truncation manifests in output. Safe read-only nature is only implied by 'Get'.

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

Conciseness5/5

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

Two dense sentences, output contract front-loaded, filter semantics second. No redundant restatement of the tool name or title, and every clause contributes new information.

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 four-parameter read tool with no output schema, the description covers the return structure and the one ambiguous parameter adequately. It falls slightly short on ref lifecycle and truncation behavior, which an agent would want to know before relying on refs across navigations.

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

Parameters4/5

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

Schema coverage is 75% and the schema already documents tabId, ref, and maxChars. The description adds genuine meaning for the one undocumented parameter, filter, spelling out that 'interactive' is the default and lists only buttons, links and inputs while 'all' adds headings, text and images – details absent from the enum schema.

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?

States a specific verb and resource ('Get a structured outline of the page') and specifies exactly what the output contains: elements with role, name, and ref ID. It implicitly distinguishes itself from siblings like get_page_text and screenshot by framing the result as an element-level outline with actionable refs.

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?

Explains the downstream workflow clearly ('a ref ID to use with click/type/form_input'), which tells the agent to call this before interaction tools. It also documents the default filter and what each mode returns. It lacks an explicit exclusion, e.g. 'use get_page_text instead when you need raw text,' so it falls short of a 5.

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