Skip to main content
Glama

web_fetch

Fetch a URL and return clean, readable content in Markdown, with page boilerplate stripped. Supports JavaScript rendering for single-page apps and term-based filtering.

Instructions

Fetch a URL and return clean, readable content — Markdown by default (structure preserved: headings, lists, links, code, tables), with page boilerplate (nav/footer/cookie bars) stripped via readability extraction. Far fewer tokens than a raw text dump. format='text' for plain text, 'html' for raw HTML (raw_html=true is an alias). Static HTTP fetch by default; render=true loads the page in headless Chromium so client-rendered/SPA content is captured (runs all JS, then extracts) — pass project to render a page behind that project's login (host fetch tools can't). contains=[words] only returns the content if the page contains the term(s) (contains_mode any|all), else omits it to save tokens. save=true (or save_path) writes the full content to disk and returns saved_path. TLS verified by default (verify_ssl=false for dev certs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to fetch
saveNoWrite the full (un-truncated) content to data/fetches/ and return saved_path (default: false).
formatNoOutput shape (default: markdown). markdown = readable structured Markdown; text = readable plain text; html = raw HTML.
renderNoLoad in headless Chromium and run JS before extracting (default: false). Use for client-rendered/SPA pages where a static fetch returns little. Slower than static.
projectNoWith render=true, load the page in this project's authenticated context — read pages behind a login.
containsNoOnly return content if the page contains these term(s) (case-insensitive). Otherwise content is omitted (matched=false) to save tokens.
raw_htmlNoAlias for format='html' (default: false).
readableNoExtract main content, dropping nav/footer/boilerplate (default: true). false = whole-page dump. Ignored for format=html.
save_pathNoExplicit file path to save to (implies save=true).
max_lengthNoMax returned content length in characters (default: 50000). Saved files are never truncated.
verify_sslNoVerify TLS certificates (default: true). Set false for self-signed certs on local/dev servers.
contains_modeNoMatch if ANY term is present (default) or require ALL.
Behavior5/5

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

With no annotations, the description carries full burden and excels: it explains default readability extraction, static vs headless rendering, TLS verification, contains filtering mode, save behavior, and aliases. No contradictions with missing 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 a single paragraph that is front-loaded with the main purpose. Every sentence adds value, though it is somewhat long. Could be slightly more structured, but remains reasonably concise for the complexity.

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?

Although there is no output schema, the description covers many aspects: conditional return with contains, saved_path from save, and format options. It lacks an explicit return structure, but is fairly complete given the tool's complexity.

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 significant value by explaining parameter contexts (e.g., 'Slower than static' for render, 'contains_mode any|all', alias for raw_html). It enriches understanding beyond the schema alone.

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 a URL and returns clean readable content, with Markdown as default. It distinguishes from siblings by mentioning token savings and the ability to render SPAs, and contrasts with raw text or HTML via format options.

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?

Provides clear guidance on when to use various parameters like render for SPAs, format for output type, contains for filtering, and project for authenticated pages. However, it lacks explicit 'when not to use this tool' guidance compared to siblings like get_page_html.

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/segentic-lab/periscope-mcp'

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