Skip to main content
Glama

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

Preview Webpage as Clean LLM Markdown (Free)

preview_webpage_markdown_free
Read-onlyIdempotent

Extracts title, token estimate, and a 450-character clean Markdown preview from any public URL at $0.00.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http/https URL

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?

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the response contains exactly a title, a token estimate and a 450-character Markdown preview, and the call is free. It does not cover error behavior for non-HTML or unreachable URLs, or any rate limits.

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?

One front-loaded sentence that names the outputs, the input scope, and the cost with no filler or redundancy.

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?

For a one-parameter, annotation-covered read tool with no output schema, the description supplies the return shape and cost, which is most of what an agent needs. Remaining gaps are edge-case behavior (non-HTML pages, truncation semantics beyond the character cap).

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 parameter at 100% schema coverage, where the schema already documents it as a "Public http/https URL". The description's only restatement is "any public URL", which adds no format or constraint 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ("Extracts") with the exact fields returned (title, token estimate, 450-character Markdown preview) and the input scope (any public URL). The "free"/$0.00 framing implicitly separates it from the paid scrape_webpage_markdown_x402 sibling, but the contrast is never stated outright.

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?

The 450-character cap and $0.00 cost imply this is a cheap preview step rather than a full extraction, but the description never says when to prefer it over scrape_webpage_markdown_x402 or buy_30day_agent_pass_x402, and gives no exclusions or prerequisites.

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.