Skip to main content
Glama

AnswerRail AEO, Schema.org & /llms.txt Audit MCP

Extract Clean Byte-0 Markdown & Schema Tables from URL

extract_byte0_markdown
Read-onlyIdempotent

Strips JavaScript hydration payloads, theme DOM bloat, and inline SVGs/CSS from a live web page URL, returning clean GitHub-Flavored Markdown (GFM) with front-loaded Schema.org tables that fit within the 25,000-token LLM context window. Use this tool when you need to read the actual text, pricing tables, or FAQs of a web page without HTML truncation; do not use it for a pass/fail readiness score (use audit_ai_readiness instead) or to generate /llms.txt manifests (use generate_ai_manifests instead). Preserves the exact URL path and query string passed in url rather than normalizing to the root domain. Read-only HTTP extraction; requires no API key, allows 60 req/min, and returns an isError flag if the remote URL returns HTTP 4xx/5xx or times out after 8 seconds.

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

Input Schema

NameRequiredDescriptionDefault
urlYesFully qualified HTTPS URL of the specific web page to convert into clean Markdown (e.g., "https://vercel.com/pricing"). Defaults to HTTPS if scheme is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Fully qualified URL of the web page to convert into Byte-0 Markdown (e.g., \"https://vercel.com/pricing\")."New value: +"Fully qualified HTTPS URL of the specific web page to convert into clean Markdown (e.g., \"https://vercel.com/pricing\"). Defaults to HTTPS if scheme is omitted."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/open-world, and the description still adds substantial behavior: what gets removed (hydration payloads, theme DOM, inline SVG/CSS), the 25,000-token output ceiling, 60 req/min rate limit, no API key requirement, 8-second timeout, and the isError condition on 4xx/5xx. These are the operational details an agent needs to plan and retry correctly.

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?

Three sentences, purpose front-loaded before cautions and sibling routing. Dense but essentially all load-bearing; the final sentence packs rate limit, timeout, and error signaling together, which is slightly crowded but still parseable.

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?

There is no output schema, yet the description characterizes the return value (clean GFM with front-loaded Schema.org tables, bounded to the context window) and the failure mode. Combined with the single fully documented parameter, there is no material gap for an agent deciding to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter at 100% schema coverage, the schema already carries the baseline. The description nonetheless adds real semantics the schema does not: the exact URL path and query string are preserved rather than normalized to the root domain, which matters for correctness on multi-page sites.

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?

States a specific verb and resource ("strips ... from a live web page URL, returning clean GitHub-Flavored Markdown") plus a distinctive output trait (front-loaded Schema.org tables). It also names the sibling tools it is not (audit_ai_readiness, generate_ai_manifests), so the agent can discriminate without opening schemas.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use trigger ("read the actual text, pricing tables, or FAQs ... without HTML truncation") and explicit when-not conditions with the correct alternative named for each redirect. Nothing is left to inference about routing.

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.