Skip to main content
Glama

web_read

Reads the visible text of a browser tab, including the page title and URL, to extract content for analysis or summarization. Use it to inspect active or specified tabs.

Instructions

Read the visible text of the page (document.body.innerText), with title and URL.

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": "web_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_charsNoDefault 40000.
target_idNoTab id from web_tabs. Omit to use the first/active tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden; it does reveal the exact extraction source (document.body.innerText) and that title and URL accompany the text. It is silent on important behavior for a browser tool: whether the page must be loaded first, whether it waits for the page, how iframes or hidden elements are treated, and what happens when the text exceeds max_chars.

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 tight sentence with the core action front-loaded and no filler. It is efficient, though so spare that a few more clauses of behavioral detail would have fit without bloat.

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 annotations and no output schema, the description usefully compensates by naming the returned fields (text, title, URL). However, for a browser-reading tool it omits prerequisites (an open/loaded tab), truncation behavior, and any contrast with sibling read tools, leaving meaningful gaps.

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%, so both max_chars and target_id are already documented in the schema, making the baseline 3. The description adds nothing about either parameter, notably not explaining truncation semantics when max_chars is hit.

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 states a specific verb and resource ('Read the visible text of the page') and even names the extraction mechanism (document.body.innerText) plus the extra fields returned (title and URL). It does not differentiate from siblings such as web_html or web_eval, so an agent must infer the boundary between rendered text and raw HTML.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no mention of any alternative such as web_html for source markup. Usage is only implied by the phrase 'visible text', leaving the agent to guess whether this tool should be preferred over HTML or eval-based extraction.

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