Skip to main content
Glama
Sign In
MCP Server for Stealth Web Search and Fetching

MCP Server for Stealth Web Search and Fetching

by maxylev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Web Fetch

webfetch
Read-only

Fetch web pages with a JavaScript-capable stealth browser and return the main content as Markdown, stripping images, scripts, and styles to reduce token bloat.

Instructions

Fetch a web page in a JavaScript-capable stealth browser and return its main content as Markdown, with images, scripts and styles stripped. Long output is paginated.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of the page to fetch.
templateNo'auto' (detect from the URL), a template name (github-repo, github-issue, npm-package, pypi-package, crates-package, docs-rs, javadoc, docs-page, docker-hub, wikipedia, gitlab, reddit, mdn-web-docs, devto, go-pkg, youtube, raw), or an inline JSON template. 'raw' converts the whole page with minimal filtering.auto
max_lengthNoMaximum characters to return. Default: 10000.
block_mediaNoBlock images, media and fonts at the network layer. Default: true.
start_indexNoOffset in characters (Unicode code points) for pagination. Default: 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv4.0.0
    • changedInput schema / properties / block_media / description
      Previous value: -"Block images, videos, and fonts entirely at the network layer. Default is true."New value: +"Block images, media and fonts at the network layer. Default: true."
    • changedInput schema / properties / max_length / description
      Previous value: -"Maximum characters to return per request. Default is 10000."New value: +"Maximum characters to return. Default: 10000."
    • changedInput schema / properties / start_index / description
      Previous value: -"Character offset for pagination. Default: 0."New value: +"Offset in characters (Unicode code points) for pagination. Default: 0."
    • changedInput schema / properties / template / description
      Previous value: -"Template to use: 'auto' (auto-detect from URL), a built-in page template name (wikipedia, reddit, mdn-web-docs, gitlab, youtube, devto, go-pkg, javadoc, github-repo, github-issue, npm-package, pypi-package, crates-package, docker-hub, docs-rs, docs-page), 'raw' for minimal-filtering full-page output, or inline JSON."New value: +"'auto' (detect from the URL), a template name (github-repo, github-issue, npm-package, pypi-package, crates-package, docs-rs, javadoc, docs-page, docker-hub, wikipedia, gitlab, reddit, mdn-web-docs, devto, go-pkg, youtube, raw), or an inline JSON template. 'raw' converts the whole page with minimal filtering."
    • changedInput schema / properties / url / description
      Previous value: -"The full URL of the webpage to fetch (must start with http/https)."New value: +"Absolute http(s) URL of the page to fetch."
  2. Changed7 schema fields changedv3.3.4
    • addedInput schema / properties / max_length / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / max_length / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / max_length / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / start_index / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / start_index / minimum
      Added value: +0
    • changedInput schema / properties / start_index / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / url / format
      Added value: +"uri"
  3. First observedv3.3.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: rendering happens in a JavaScript-capable stealth browser, output is reduced to main content as Markdown with images/scripts/styles stripped, and long results are paginated. It stops short of rate limits, auth, or how pagination should be driven.

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 tightly packed sentences with no filler, front-loading the core action before the extraction and pagination details. Every clause earns its place.

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?

With no output schema, the description carries the return-value burden and does so: Markdown main content, stripped media, paginated output. All five parameters are schema-documented and annotations cover the open-world read-only nature. Minor gaps are error behavior and how to continue pagination.

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 documented in the schema itself, which sets the baseline at 3. The description's only parameter-relevant additions are the Markdown/media-stripping behavior (mapping loosely to block_media) and 'Long output is paginated' (mapping to start_index/max_length), neither of which adds syntax or semantics 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?

The description gives a specific verb ('Fetch') and resource ('a web page') plus the processing pipeline (JS-capable stealth browser, main content as Markdown, media stripped). This clearly separates it from the sibling websearch, though it never names websearch explicitly as the search-oriented alternative.

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?

Usage is only implied: you call this when you have a URL whose page content you want. There is no statement of when to prefer this over websearch, no prerequisites, and no mention of failure modes for unreachable or JS-blocked pages.

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

Deploy Server

Other Tools