x402-weblens-mcp

Clean page text ($0.005)

weblens_extract

Extracts the main content of a web page as clean Markdown, removing ads, menus, and popups so AI agents can read the page without clutter.

Instructions

Get the main content of a web page as clean Markdown, without ads, menus or popups. Costs $0.005 USDC.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) URL of the page

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Nov 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the valuable fact that calls cost $0.005 USDC and that chrome noise is stripped, but says nothing about JS rendering, paywalls, redirects, truncation of long pages, or failure behavior for a fetch that can be expensive per call.

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?

Two short sentences with zero filler, leading with the capability and following with the cost. Nothing redundant is included and no important constraint is buried.

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 read tool with no output schema and no annotations, the definition covers purpose, output format, and cost, which is most of what an agent needs. Missing are edge-case behaviors (JS-heavy or paywalled pages, output size) that would matter for reliability but are secondary at this complexity.

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?

A single parameter with 100% schema description coverage already defining it as a "Public http(s) URL", so the schema does the semantic work and the description adds little beyond that. The implicit constraint to public pages is consistent with, but not beyond, the schema.

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 ("Get the main content of a web page") plus the output format ("as clean Markdown") and an explicit exclusion list ("without ads, menus or popups"). It is clear what the tool does and implicitly how it differs from link/metadata-oriented siblings, though no sibling is named 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?

There is no explicit when-to-use or when-not-to-use sentence, but the stated purpose (want the readable main text rather than the full DOM) combined with the "Costs $0.005 USDC" note gives an agent enough context to infer the appropriate scenario. Alternatives such as weblens_structure or weblens_links are not addressed.

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

Deploy Server