Skip to main content
Glama

WebLens

by dev.weblens
OverviewDiscussionsAdmin

fetch_webpage

Fetch and convert any webpage to clean markdown. Fast, no JavaScript rendering. Perfect for static content, articles, and documentation. Price: $0.002 (70% off when served from cache); an x402 payment is at least $0.004

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to process
cacheNoServe a cached copy when one exists (cached responses are 70% off)
timeoutNoRequest timeout in milliseconds
waitForNoCSS selector to wait for (Pro tier only)
cacheTtlNoHow long to cache this response, in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / example
      Previous value: -"https://example.com/article"New value: +"https://example.com"
  2. Changed13 schema fields changed
    • addedInput schema / properties / cache / default
      Added value: +true
    • changedInput schema / properties / cache / description
      Previous value: -"Serve from cache when available (default true; cached responses cost 70% less)"New value: +"Serve a cached copy when one exists (cached responses are 70% off)"
    • addedInput schema / properties / cache / example
      Added value: +true
    • addedInput schema / properties / cacheTtl / default
      Added value: +3600
    • changedInput schema / properties / cacheTtl / description
      Previous value: -"Cache TTL in seconds (default 3600)"New value: +"How long to cache this response, in seconds"
    • addedInput schema / properties / cacheTtl / example
      Added value: +3600
    • addedInput schema / properties / timeout / default
      Added value: +10000
    • changedInput schema / properties / timeout / description
      Previous value: -"Request timeout in ms (default 10000)"New value: +"Request timeout in milliseconds"
    • addedInput schema / properties / timeout / example
      Added value: +10000
    • changedInput schema / properties / url / description
      Previous value: -"The URL to fetch"New value: +"The URL to process"
    • addedInput schema / properties / url / example
      Added value: +"https://example.com/article"
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / properties / waitFor
      Added value: +{
+  "description": "CSS selector to wait for (Pro tier only)",
+  "type": "string"
+}
  3. First observed

TDQS

A3.7/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 disclose meaningful traits beyond schema: a static-only, no-JS rendering limitation, a speed claim, and an explicit cost model including the x402 payment minimum. It omits failure/retry and redirect behavior, but the cost disclosure is genuinely useful for a paid tool.

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 short sentences, front-loaded with the core purpose and output format before the cost note. The pricing detail is relevant for a metered tool and does not feel padded, though it is stated twice (per-call and per-cache).

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 tool with no output schema and no annotations, the description covers purpose, output format, static-content limitation, and cost sufficiently to call it correctly. Remaining gaps (failure modes, whether redirects are followed) are minor for a fetch-and-convert utility.

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?

Schema description coverage is 100%, so all five parameters are already documented in the schema. The description adds no parameter-level syntax or format detail, so the baseline of 3 applies. The schema's 'waitFor (Pro tier only)' note is not reconciled by the description.

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+resource (fetch a webpage) and the output transformation (convert to clean markdown), which is more than a restatement. It also scopes itself with 'no JavaScript rendering,' implicitly differentiating it from the JS-capable siblings like fetch_webpage_pro, though it names no sibling explicitly.

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?

'Perfect for static content, articles, and documentation' implies when to use it, and 'no JavaScript rendering' implies the exclusion of JS-heavy pages. However, no alternative tool is named for those excluded cases, so the routing is left to inference.

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

All WebLens toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources