Skip to main content
Glama

fetch_url

Read-onlyIdempotent

Fetch a URL and extract clean, readable content with an excerpt and link list. Ideal for reading articles or gathering outbound links from known pages.

Instructions

Fetch one URL, extract readable content (Readability-style), and return a compact excerpt plus link list. The full extracted text is preserved in hidden _meta.full_text. Best for: reading a known page after search/search_many, extracting clean prose from an article, getting an outbound-link list from a hub page. Returns: {title, url, excerpt, citations, links, content_type, render_mode} plus domain and word/char counts. Rendered fetch is automatic for JS-heavy pages; pass rendered=true to force browser mode when a previous fetch came back nearly empty. Use fetch_many for multiple URLs in one call; search_and_fetch if you do not yet have URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute http:// or https:// URL to fetch. Bare domains like 'example.com' are auto-prefixed with https://. Other schemes are rejected.
max_excerpt_charsNoExcerpt character cap for the visible output (200–50000). Default comes from server settings. The full extracted text is always returned in hidden `_meta.full_text`.
max_linksNoMaximum outbound links to surface in the visible output (0–64, default 8). The complete link list is always included in hidden `_meta`.
renderedNoForce browser-based rendering for fetches. Default false: the server auto-renders only when a page is JS-heavy or returns near-empty text. Set true when a previous fetch came back nearly empty or to read a known SPA. Forced rendering is several times slower than HTTP fetch.
render_wait_msNoExtra milliseconds to wait after DOM content load before extracting (0–15000). Use a higher value (e.g. 1500–4000) for SPAs that hydrate slowly.
ttlNoCache TTL override in seconds (0–86400). 0 disables caching for this call. Omit to use the server's default TTL.
Behavior5/5

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

Annotations provide readOnlyHint, destructiveHint, idempotentHint. Description adds auto-prefixing of bare domains, hidden full text, automatic rendering for JS-heavy pages, and performance trade-offs.

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?

Well-organized: main action, best-for list, return format, parameter details. Every sentence adds value without redundancy.

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?

Comprehensive for a tool with 6 parameters and no output schema. Covers return structure, hidden fields, cache, rendering modes, and usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%. Description adds context beyond schema: url scheme handling, default excerpt chars from server, force rendering behavior, and TTL cache override meaning.

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?

Clearly states 'Fetch one URL, extract readable content' and lists return fields. Distinguishes from siblings like fetch_many and search_and_fetch.

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 provides 'Best for' scenarios and when to use alternatives. Includes guidance on force rendering when previous fetch returns empty.

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/88plug/searxng-mcp'

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