Skip to main content
Glama
ymylive
by ymylive

fetch

Read-onlyIdempotent

Retrieve the main content of a single URL as reader-mode Markdown or JSON. Ideal when you already have a URL and need clean text for verifying claims, avoiding ads, nav, or scripts. Supports caching and custom rendering for JavaScript-heavy pages.

Instructions

Fetch one URL and return reader-mode Markdown of the main content.

Best for:
- You already have a URL (from `search`, the user, or your own knowledge)
  and need the actual page text.
- Verifying a single claim by reading the source.
- Pages that need reader-mode cleanup (nav/footer/scripts stripped).

Not recommended for:
- Multiple URLs at once -> use `fetch_batch` (concurrent, one round-trip).
- "Search then read top N" -> use `research` (one call, not two).
- PDF/DOCX URLs -> use `read_doc` (proper binary parsing).
- You don't have a URL yet -> use `search` first.

Returns:
- markdown (default): a small header (URL, render method, token count)
  plus the cleaned page body.
- json: {url, title, content, method, truncated, tokens_estimated,
  author, published_date, sitename}.

Common mistakes:
- Passing a search query instead of a URL.
- Using `render="http"` on a JS-only SPA — it returns near-empty content;
  use "auto" (default) or "browser".
- Forgetting that results are cached 7 days — use `force_refresh=True`
  or `max_age_hours=0` for a fresh pull.

Args:
    url: Absolute http(s) URL.
    render: "auto" (try HTTP, fall back to stealth Chromium), "http"
        (fast, fails on JS), "browser" (slow, robust).
    force_refresh: Bypass the page cache entirely.
    max_age_hours: Treat cached pages older than this as a miss. 0 = same
        as force_refresh. None = server default TTL (7 days).
    format: "markdown" or "json".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
renderNoauto
force_refreshNo
max_age_hoursNo
formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and openWorldHint, so the description's job is to add context. It does so by explaining caching behavior (7-day cache, force_refresh, max_age_hours), rendering methods (auto, http, browser), return format details, and common pitfalls (e.g., JS-heavy pages). However, it does not explicitly state that the tool is read-only or idempotent, but the annotations cover that. One slight gap: the description doesn't mention rate limits or any side effects beyond cache.

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 with clear sections (Best for, Not recommended for, Returns, Common mistakes, Args). It is comprehensive but not overly verbose; every sentence adds value. Slightly longer than necessary due to repetition in Common mistakes (e.g., already covered by Not recommended for), but still efficient overall.

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 5 parameters (1 required), existing annotations, an output schema (not shown but exists), and sibling tools, the description is complete. It covers purpose, guidelines, parameter semantics, caching, rendering options, common mistakes, and return format. The output schema likely defines the return structure, so the description's summary is sufficient.

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 description coverage is 0%, meaning the description must fully explain parameters. It does: url (absolute http(s)), render (three options with tradeoffs), force_refresh (bypass cache), max_age_hours (TTL control), format (markdown/json). Each parameter gets meaningful context beyond the schema's default/enum values. However, it doesn't explain the exact behavior of max_age_hours when null (though it says 'server default TTL'), which is a minor gap.

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 'Fetch one URL and return reader-mode Markdown of the main content', specifying the verb (fetch), resource (one URL), and output format (reader-mode Markdown). The 'Best for' and 'Not recommended for' sections further differentiate from sibling tools like fetch_batch, research, read_doc, and search, making the purpose very specific and well-defined.

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?

The description has explicit sections for 'Best for' (when to use) and 'Not recommended for' (when not to use), with clear alternatives provided (fetch_batch, research, read_doc, search). It also lists common mistakes to avoid, giving agents comprehensive guidance on proper usage.

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/ymylive/free-search-mcp'

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