Skip to main content
Glama

read_text

Read-only

Extract visible text from a page or element as plain text to read articles, tables, and results. Use an element ref or read the whole page.

Instructions

Get the visible text of the page, or of one element, as plain text. Good for reading articles, tables and results.

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_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoElement ref from the latest snapshot, e.g. "e14".
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
maxCharsNoDefault 20000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the description only needs to add context — and it does contribute the 'visible text' scoping (hidden content is excluded) and the page-vs-element choice. It does not address truncation behavior when output exceeds maxChars, nor what 'visible' means for off-screen or collapsed content.

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 short sentences with the primary capability front-loaded and the use-case hint trailing, with no redundant restatement of the schema.

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?

A simple read-only tool with zero required parameters and no output schema; the description conveys scope and output type adequately. The only real gap is truncation semantics when maxChars is hit, which an agent would want to know before relying on the text.

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 ref, tab and maxChars are already documented inline. The phrase 'or of one element' loosely ties to the ref parameter but adds no format or fallback detail beyond the schema, so the baseline of 3 applies.

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 ('Get'), a specific resource ('visible text of the page, or of one element'), and the return format ('plain text'), which separates it from script-evaluation tools like run_js. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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?

'Good for reading articles, tables and results' gives an implied use case, but there is no statement of when to prefer this over run_js or console_messages, and no prerequisites such as needing a ref from the latest snapshot.

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