Skip to main content
Glama
georgittanchev

web-tools-mcp-server

Web Fetch

web_fetch
Read-onlyIdempotent

Fetch web page content while bypassing anti-bot blocks using rotating user agents, proxy support, and automatic fallback to Jina Reader for clean markdown.

Instructions

Fetch the contents of a web page with anti-detection capabilities.

This tool replaces the native web_fetch. It uses rotating real-browser user agents, optional proxy (Bright Data or any HTTP/SOCKS5), and automatic fallback to Jina Reader API for sites that block direct access.

Three fetch strategies:

  • "auto" (default): Tries direct fetch first (with UA rotation + proxy if configured). If blocked (403/429/503/captcha), automatically falls back to Jina Reader.

  • "direct": Direct HTTP fetch only. Uses rotating browser user agents and your configured proxy. Returns raw HTML.

  • "jina": Uses Jina Reader API exclusively. Best for JS-heavy sites. Returns clean LLM-ready markdown. Handles rendering server-side.

For fetching multiple URLs at once, use web_bulk_fetch instead — it's faster and uses a single tool call.

Args:

  • url (string, required): The URL to fetch. Must include https:// or http://.

  • strategy (string, optional): "auto", "direct", or "jina". Default: "auto".

Returns: Page content (HTML for direct, markdown for Jina), HTTP status, final URL after redirects, and which strategy was used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull URL to fetch, must include https:// or http://
strategyNoFetch strategy: 'auto' (try direct with proxy+UA rotation, fallback to Jina Reader), 'direct' (only direct fetch with rotating UA + optional proxy), 'jina' (only Jina Reader — best for JS-heavy sites and anti-bot bypassing)auto
Behavior5/5

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

Adds significant behavioral detail beyond annotations: rotating user agents, optional proxy, fallback to Jina Reader on blocks, and the ability to choose strategies. It also discloses the return format (HTML vs markdown) and the included status/final URL/strategy, enriching the tool's operational model.

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?

Despite being detailed, the description is well-structured with clear sections (purpose, strategies, alternative, args, returns). Each sentence contributes valuable information without redundancy, and the front-loaded core purpose makes it easy to scan.

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

Completeness5/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 compensates by detailing return values (page content, HTTP status, final URL, strategy used). It covers tool alternatives, strategy selection, and parameter semantics thoroughly, making it self-sufficient for an agent to select and invoke successfully.

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?

Schema coverage is 100%, but the description adds extra meaning by explaining the strategies in depth (auto, direct, jina) and how they behave, including fallback logic and output format differences. This goes beyond the schema's brief parameter descriptions, enhancing the agent's understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description clearly states the tool fetches web page contents with anti-detection capabilities, specifying the verb 'Fetch' and resource 'contents of a web page'. It distinguishes itself from sibling web_bulk_fetch by noting that the latter is for multiple URLs, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises using web_bulk_fetch for multiple URLs, and details when to use each strategy (e.g., 'jina' best for JS-heavy sites). The 'auto' strategy's fallback behavior is explained, providing clear when-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/georgittanchev/mcp-search'

If you have feedback or need assistance with the MCP directory API, please join our Discord server