Skip to main content
Glama
web-insights-mcp
by nqcthedev

Fetch page as Markdown

fetch_page
Read-onlyIdempotent

Download a web page as clean Markdown with its main content and metadata, enabling reliable reading, summarization, quoting and fact-checking of a specific URL.

Instructions

Download a web page and return its main readable content as clean Markdown (navigation, ads, scripts and boilerplate removed, links made absolute) plus title, meta description, language, canonical URL and word count. Use this whenever you need to read, summarise, quote or fact-check a specific URL. mode "article" (default) uses Mozilla Readability for articles/blog posts/docs; use mode "full" for home pages, landing pages or listings where the article detector would drop content. Output is truncated to max_chars.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "fetch_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL. A bare domain like example.com is treated as https://example.com.
modeNo"article" = main article only (Readability); "full" = the whole <main>/<body> minus header/nav/footer.article
max_charsNoMaximum Markdown characters to return. Lower it to save context; raise it for long documents.
include_linksNoAlso return up to 100 links found on the page.

Output Schema

NameRequiredDescriptionDefault
urlYes
langYes
bytesYes
linksNo
titleYes
bylineYes
statusYes
finalUrlYes
markdownYes
siteNameYes
canonicalYes
elapsedMsYes
extractorYes
fromCacheYes
openGraphYes
truncatedYes
wordCountYes
descriptionYes
publishedTimeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new behavior: boilerplate/nav/ads/scripts are stripped, links are made absolute, and output is truncated to max_chars. It doesn't cover failure modes (blocked pages, paywalls, non-HTML responses), which is the main remaining gap.

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?

It is front-loaded with the payload — what is returned — before usage and mode advice, and essentially every clause carries information. It runs as one dense paragraph, which makes the mode-selection guidance slightly harder to scan than a short bulleted split would be.

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?

With an output schema, full schema coverage and rich annotations already supplied, the description only needs to add what those fields cannot: content-cleaning behavior and mode selection, both of which it covers. Truncation is flagged; error/failure behavior for unreachable pages is the one notable omission.

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 100%, so the baseline is 3 and the schema already documents every parameter. The description still adds decision-level meaning for mode by explaining the outcome each value produces (article detector dropping content on listings) rather than just restating the enum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Download a web page and return its main readable content as clean Markdown" gives a specific verb and resource, and the enumeration of returned fields (title, meta description, language, canonical URL, word count) pins down the output precisely. The phrase "a specific URL" implicitly separates it from multi-page siblings like crawl_site, but no sibling is named outright.

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?

"Use this whenever you need to read, summarise, quote or fact-check a specific URL" gives a clear use context, and the mode guidance adds a concrete when-to-use-which rule (article for posts/docs, full for home pages and listings where the detector drops content). No explicit alternative tool or exclusion is named, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.