Skip to main content
Glama

Get the plain visible text of a web page (no HTML, scripts or styles), whitespac

page_text
Read-only

Get the plain visible text of a web page (no HTML, scripts or styles), whitespace-normalized, with title and word count. Optional maxChars (1,000-200,000, default 50,000). Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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": {
      "url": "<url>"
    },
    "name": "page_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.
maxCharsNoMax characters (1000-200000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses whitespace normalization, returned title and word count, expected speed, free quota, and paid overage mechanics. This is unusually rich behavioral context for a read-only scraper.

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?

The definition is dense and front-loaded around the core purpose, then adds relevant operational details. Pricing details are slightly heavy but still useful for an agent deciding whether it can call the tool.

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?

With no output schema, the description still explains the shape of the return: visible text, title, and word count. Combined with the schema's payment guidance, it is sufficiently complete, though it does not discuss blocked pages or dynamic-rendering limits.

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 already 100%, and the schema documents url, payment, and maxChars. The description adds a default value for maxChars, but otherwise the schema carries the parameter semantics.

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 states a specific verb and resource: extract the plain visible text of a web page, explicitly excluding HTML, scripts, and styles. It also distinguishes the output shape from likely siblings such as page_markdown by specifying whitespace-normalized text plus title and word count.

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?

The description clearly implies when to use this tool: when an agent wants visible page text rather than markup or analysis. It does not explicitly name alternatives such as page_markdown, but the plain-text scope gives strong context for selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.