Skip to main content
Glama

Web Fetch (full page)

web_fetch
Read-only

Fetch any web page and return its full content as clean Markdown, with browser-like headers to bypass bot filters. Choose between main content only, full page, or raw HTML.

Instructions

Fetch ANY web page directly and return its FULL content as clean Markdown (not a summary). Uses browser-like headers to get past common bot filters that block naive/robots-respecting clients (e.g. 403/202 to non-browser clients). Requests go straight to the target site; HTML is converted to Markdown locally (no third-party proxy/reader). Content is found by selecting the page's main content region and pruning navigation rails, so surrounding chrome is left out without ever risking the article. mode='article' (default) returns that region; mode='full' keeps the whole page body; mode='raw' returns unconverted HTML. Does NOT solve full JS/Cloudflare challenge pages or CAPTCHAs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to fetch (scheme optional; https assumed)
modeNoarticle=main content only (default), full=whole body, raw=unconverted HTML, outline=heading structure with each section's size, for deciding what to request
linksNoinline (default) keeps Markdown link targets; 'none' keeps link text but drops the URLs, which cuts a large share of the output on link-heavy pages
sectionNoReturn only the section with this heading, plus anything nested under it. Matched case-insensitively on a substring. Use mode='outline' first to see what a long page contains.
max_charsNoOptional cap on returned characters (truncates with a note); omit for full content
Behavior5/5

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

The description reveals important behavioral traits not covered by annotations: uses browser-like headers, converts HTML to Markdown locally, selects main content region, and explains modes. No contradiction with annotations.

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?

The description is well-structured and information-dense, starting with the core purpose and then detailing modes and limitations. It could be slightly more concise, but each sentence adds value.

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?

Given the tool's 5 parameters and no output schema, the description covers all aspects: modes, parameter behavior, limitations, and use cases. It is thorough enough for an AI agent to use correctly.

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?

While the input schema describes all parameters, the description adds context such as default modes, the purpose of each mode, and the interplay between parameters (e.g., using 'outline' before 'section'). This enhances understanding beyond the schema.

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 any web page and returns full content as clean Markdown, distinguishing it from the sibling 'web_search' which likely returns search results.

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

Usage Guidelines4/5

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

The description explains when to use the tool (fetching full pages, bypassing bot filters) and its limitations (cannot solve JS/Cloudflare challenges or CAPTCHAs). However, it does not explicitly compare to the sibling tool 'web_search'.

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/pzalutski-pixel/netlens-mcp'

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