Skip to main content
Glama

Web Scraper Markdown Reader, Live Search & Agent Pass x402 MCP

Full Webpage-to-Markdown & JSON-LD Extractor ($0.015 USDC via x402)

scrape_webpage_markdown_x402
Read-onlyIdempotent

Converts any public webpage into up to 24,000 chars of clean LLM Markdown, JSON-LD, and outbound links ($0.015 USDC on Base via x402 or 30d Pass).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic webpage URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. Beyond that the description discloses the 24,000-character output cap, the three payload components (Markdown, JSON-LD, outbound links), and the payment mechanism ($0.015 USDC on Base via x402 or a 30d Pass), which is meaningful context the agent would otherwise lack.

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?

A single dense sentence that front-loads the conversion outcome and appends output size, payload types, and cost. Nothing is wasted, though the parenthetical pricing clause is slightly tangled and could be split for scannability.

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 one-parameter, read-only extraction tool with no output schema, the description covers the output composition, size ceiling, and cost model — the facts an agent needs to decide and pay. No meaningful gap remains beyond edge-case error behavior.

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, so the baseline is 3. The description adds only the constraint that the target must be a 'public webpage', which aligns with the schema's 'Public webpage URL' wording rather than extending it.

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?

The description states a specific verb and resource ('Converts any public webpage into... Markdown, JSON-LD, and outbound links') and enumerates the returned artifacts, so the agent knows exactly what the tool produces. It never names or contrasts itself with the free 'preview_webpage_markdown_free' sibling, so differentiation is left to the agent.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. Given a free preview sibling exists, the most important routing question — when to pay $0.015 versus use the free preview — is never addressed; the description only states that a paid x402 path and a 30d Pass exist.

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.