Skip to main content
Glama
vojtisprime11

mcp-server-web-fetcher

Fetch page as Markdown

fetch_page_markdown
Read-onlyIdempotent

Fetches a web page and converts it to clean Markdown for reading or analysis, removing scripts, styles, and ads while preserving tables, code blocks, and lists.

Instructions

Fetch a web page and convert it to clean Markdown for reading or analysis. Removes scripts, styles, ads and (by default) navigation chrome, resolves relative links to absolute URLs, and keeps tables, code blocks and lists intact. Long pages are paginated: when truncated is true, call again with startIndex: nextStartIndex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of the page to fetch.
maxLengthNoMaximum number of Markdown characters to return in one call.
timeoutMsNoRequest timeout in milliseconds (1000-120000).
startIndexNoCharacter offset to start from. Use `nextStartIndex` to page through long pages.
includeLinksNoKeep Markdown links. When false, link text is inlined as plain text.
includeImagesNoKeep images as Markdown image syntax.
includeMetadataNoInclude a short metadata summary (title, description, canonical, language).
mainContentOnlyNoStrip navigation, headers, footers and sidebars, keeping the densest content block.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFinal URL after redirects.
titleYes
statusYes
endIndexYes
markdownYes
metadataYes
elapsedMsYes
fromCacheYes
redirectsYes
truncatedYes
wordCountYes
startIndexYes
contentTypeYes
totalLengthYesLength of the full Markdown document.
requestedUrlYes
markdownLengthYes
nextStartIndexYesPass as `startIndex` to fetch the next chunk, or null when complete.
bytesDownloadedYes
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. Description adds specific behaviors: removes scripts, styles, ads, navigation chrome (by default), resolves relative links, keeps tables/code blocks/lists, and paginates. No contradiction.

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?

Three sentences, each serving a distinct purpose: purpose, behavior details, pagination instructions. Front-loaded and no redundant information.

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 the number of parameters, annotations, and presence of output schema, the description covers all key behaviors (what is stripped, pagination, link/image handling) without gaps. No missing critical information.

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%, but the description adds context beyond schema (e.g., pagination mechanism, default behavior for mainContentOnly). This extra value justifies above baseline 3.

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 verb (Fetch, convert) and resource (web page, Markdown) with a specific purpose (reading or analysis). It implicitly distinguishes from siblings extract_metadata and extract_links by focusing on full-page conversion to Markdown.

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 explicit guidance on pagination ('when truncated is true, call again with startIndex: nextStartIndex') and mentions defaults. However, does not explicitly state when not to use this tool versus siblings.

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/vojtisprime11/mcp-server-web-fetcher'

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