Skip to main content
Glama

page-to-text

Fetches a public web page and returns its readable text as JSON: url, status, title, char count, and clean text with scripts, styles and tags stripped. Blocks private/localhost addresses. Free: 3 calls a day per visitor; after that $0.01 per call via x402 at https://tools.orchardshop.xyz/t/page-to-text.

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-to-text"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYese.g. https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the returned fields, the stripping behavior, an SSRF-style restriction (private/localhost blocked), and both free-tier and paid rate/cost mechanics with the x402 endpoint. It omits error semantics, redirect/JS-rendering behavior, and timeouts, which keeps it from a 5.

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?

Three tight sentences, front-loaded with what it returns, then the access restriction, then pricing. Every clause carries actionable information for an agent (fields, blocklist, quota, payment path) with no filler.

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?

There is no output schema, but the description enumerates the response fields (url, status, title, char count, text), so an agent knows what to expect. Readiness is high for a one-parameter fetch tool; only failure-mode detail (what non-2xx or blocked responses look like) is 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?

There is a single required parameter with 100% schema description coverage including an example value, so the schema already does the work. The description adds nothing about URL format, scheme requirements, or query/fragment handling beyond what the schema states.

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 and resource ('Fetches a public web page') plus the exact output shape ('readable text as JSON'). It does not name any sibling (e.g. page-to-markdown) to distinguish text output from markdown output, so an agent must infer the difference from the format wording.

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?

Constrains usage implicitly by limiting scope to 'public' pages and stating that private/localhost addresses are blocked, which tells the agent when the tool will refuse. It gives no explicit guidance on when to prefer this over page-to-markdown, bulk-page-to-markdown, or site-crawl-markdown.

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.

Resources