Web Fetch
Theweb_fetch tool does a plain HTTP GET and extracts readable content
(HTML to markdown or text). It does not execute JavaScript.
For JS-heavy sites or login-protected pages, use the
Web Browser instead.
Quick start
web_fetch is enabled by default — no configuration needed. The agent can
call it immediately:
Tool parameters
| Parameter | Type | Description |
|---|---|---|
url | string | URL to fetch (required, http/https only) |
extractMode | string | "markdown" (default) or "text" |
maxChars | number | Truncate output to this many chars |
How it works
Fetch
Sends an HTTP GET with a Chrome-like User-Agent and
Accept-Language
header. Blocks private/internal hostnames and re-checks redirects.Fallback (optional)
If Readability fails and Firecrawl is configured, retries through the
Firecrawl API with bot-circumvention mode.
Config
Firecrawl fallback
If Readability extraction fails,web_fetch can fall back to
Firecrawl for bot-circumvention and better extraction:
tools.web.fetch.firecrawl.apiKey supports SecretRef objects.
If Firecrawl is enabled and its SecretRef is unresolved with no
FIRECRAWL_API_KEY env fallback, gateway startup fails fast.Limits and safety
maxCharsis clamped totools.web.fetch.maxCharsCap- Response body is capped at
maxResponseBytesbefore parsing; oversized responses are truncated with a warning - Private/internal hostnames are blocked
- Redirects are checked and limited by
maxRedirects web_fetchis best-effort — some sites need the Web Browser
Tool profiles
If you use tool profiles or allowlists, addweb_fetch or group:web:
Related
- Web Search — search the web with multiple providers
- Web Browser — full browser automation for JS-heavy sites
- Firecrawl — Firecrawl search and scrape tools