Skip to main content
Glama

web_fetch

Fetch and read webpage content, including from bot-protected sites and package registries, with automatic fallback and pagination support.

Instructions

Fetch and read content from a URL via EnriProxy's multi-tier fetch service.

When to use:

  • When you need to read the full content of a webpage.

  • When you need to access documentation, articles, or code files.

  • When simpler fetch methods fail due to anti-bot protection.

Features:

  • Package registry API detection (npm, PyPI)

  • Raw file fetch (GitHub raw, HuggingFace)

  • Robust fetching for static, dynamic, and bot-protected sites (best-effort)

  • Automatic fallback across multiple retrieval strategies (details intentionally not exposed)

Notes:

  • Provide the full URL including protocol (https://).

  • Content is limited by the max_chars parameter (default: 200000).

  • If the result is truncated and includes a cursor, call web_fetch again with cursor + offset + limit to read more without re-fetching.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoFull URL to fetch (http:// or https://).
cursorNoOpaque cursor returned by a previous `web_fetch` call for pagination.
promptNoOptional hint describing what you want to extract (the tool returns fetched content; it does not generate an AI summary).
max_charsNoMaximum content length (default: 200000).
offsetNoLegacy alias for offset_chars. Cursor read offset in characters (default: 0).
limitNoLegacy alias for limit_chars. Cursor read limit in characters (default: max_chars).
offset_charsNoCursor read offset in characters (default: 0). Prefer this current EnriProxy field name over offset.
limit_charsNoCursor read limit in characters (default: max_chars). Prefer this current EnriProxy field name over limit.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It details features like package registry detection, raw file fetch, robust handling of bot-protected sites, and automatic fallback. It also discloses limitations ('best-effort', 'details intentionally not exposed') and pagination behavior.

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?

The description is concise and well-organized with clear sections: intro, when to use, features, and notes. Every sentence adds value without redundancy.

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 explains pagination via cursor, truncation behavior, and mentions content limits. It covers the main operational aspects, though it does not detail the exact format of returned content.

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?

Schema coverage is 100%, so baseline is 3. The description adds context for 'max_chars' default and explains cursor usage for pagination, but most parameters are already well-documented in 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 explicitly states 'Fetch and read content from a URL,' which is a specific verb and resource. It distinguishes itself from the sibling tool 'web_search' by focusing on fetching full content versus searching.

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 includes a 'When to use' section that clearly indicates appropriate scenarios (reading full webpages, documentation, code files) and even mentions when simpler methods fail. However, it does not explicitly exclude alternatives like web_search, but it provides a clear context.

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/Bedolla/EnriWeb'

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