Skip to main content
Glama
maxylev

MCP Server for Stealth Web Search and Fetching

by maxylev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Web Fetch

webfetch

Fetch a URL and return its main text content. Executes JavaScript to render dynamic pages and strips images/media to reduce token consumption.

Instructions

Fetch and extract the main text content from any webpage. Fully executes JavaScript to load React/SPAs and aggressively strips images/media (including base64) to save context tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe full URL of the webpage to fetch (must start with http/https).
templateNoTemplate 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.auto
max_lengthNoMaximum characters to return per request. Default is 10000.
block_mediaNoBlock images, videos, and fonts entirely at the network layer. Default is true.
start_indexNoCharacter offset for pagination. Default: 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. First observedv3.3.2

TDQS

A3.5/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 behavioral burden. It explicitly discloses two significant traits: full JavaScript execution to load React/SPAs and aggressive stripping of images/media to save context tokens. It does not cover failure modes, redirects, or output format, but it goes well beyond the schema.

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 sentences with zero wasted words. The primary purpose is front-loaded, and the behavioral caveat fills the second sentence. Every phrase earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers core behavior and a key side effect, and the schema handles all parameters. However, it omits usage guidance relative to the sibling websearch and does not mention the return format, pagination behavior, or how output is structured, leaving an agent to make assumptions.

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?

The schema documents all five parameters with 100% description coverage, so the baseline of 3 applies. The description itself adds no parameter-level meaning beyond the schema, and no parameter is left undocumented.

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 first sentence names a specific verb ('Fetch and extract'), a resource ('main text content'), and a scope ('any webpage'). It is clear and not tautological, but it does not explicitly contrast with the sibling tool websearch, so it falls short of full differentiation.

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?

The description gives no guidance on when to use webfetch versus websearch. There are no prerequisites, excluded cases, or alternative-routing hints, so the agent must infer appropriate usage from the schema and tool name alone.

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