Skip to main content
Glama

Page text

browser_get_text
Read-only

Extract readable page text, including PDFs, with secrets masked and no reference clutter; optionally target the first CSS match or cap characters to keep output small.

Instructions

Readable text of the page (PDFs too), secrets masked, without refs. To read a few values or a list, browser_query is far smaller.

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

Input Schema

NameRequiredDescriptionDefault
selectorNoCSS selector: only the first match's text, e.g. "main" or "#results"
max_charsNoDefault 20000. Ask for less when the start of the page is enough.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), so the description's job is to add behavior it doesn't already say — and it does: secret values are masked in the output, element refs are omitted from the returned text, and PDFs are supported. What it doesn't disclose is how truncation is signalled when 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.

Conciseness5/5

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

Two sentences, no filler. The capability and its constraints come first, and the routing to browser_query is placed last where it belongs.

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

Completeness5/5

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

For a two-parameter, zero-required read tool with no output schema, the description covers what comes back (readable text, masked secrets, no refs) and what inputs control (selector targeting, result size). Nothing an agent needs to invoke it correctly appears to be missing.

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% and both parameters are already documented, including the 20000 default and the 'ask for less' guidance. The description adds no selector semantics or format detail beyond the schema, so the baseline 3 applies.

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?

The description names a specific operation and resource — extracting readable page text — and immediately scopes it with 'PDFs too', 'secrets masked', and 'without refs'. This distinguishes it from browser_query and from snapshot-style siblings without requiring the agent to open any schema.

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?

It routes the agent explicitly: 'To read a few values or a list, browser_query is far smaller,' which gives a concrete condition for choosing the alternative. It stops short of stating when this tool should not be used at all, so the guidance is clear but not exhaustive.

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