FetchV2 MCP Server

Overview Schema Source Related Servers Discussions Admin

fetch

Retrieve a single webpage and extract its main content as clean markdown, removing navigation, ads, and boilerplate for reading articles, docs, or blogs.

Instructions

Fetch a single webpage and extract its main content as clean markdown.

USE THIS TOOL WHEN:

You need to read an article, documentation page, or blog post
You want clean, readable text without boilerplate (navbars, ads, footers)
The user provides a specific URL to read

DO NOT USE WHEN:

You need to fetch multiple URLs (use fetch_batch instead - fewer round trips)
You want to discover what pages exist on a site (use discover_links first)

PAGINATION: Large pages are automatically truncated. The response will include 'use start_index=N to continue' - call again with that value to get more content.

EXAMPLES:

fetch(url="https://docs.example.com/guide") → Get documentation page
fetch(url="https://example.com/api", max_length=2000) → Shorter response to save context
fetch(url="https://example.com/data", include_tables=True) → Preserve tabular data

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The webpage URL to fetch (must be http:// or https://)
`max_length`	No	Maximum characters to return. Use 1000-2000 for summaries, 5000 (default) for full content.
`start_index`	No	Character offset for pagination. Use the value from 'start_index=N' in truncated responses.
`get_raw_html`	No	Skip extraction and return raw HTML. Use when you need original markup or extraction fails.
`include_links`	No	Preserve hyperlinks in markdown. Enable to follow references.
`include_tables`	No	Preserve tables in markdown. Disable for text-only articles.
`include_metadata`	No	Include title, author, date at top. Disable to save tokens.
`bypass_robots_txt`	No	Skip robots.txt check. Only for user-initiated requests.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 15, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the burden and it does disclose key behaviors: boilerplate removal, automatic truncation, and pagination via start_index. It does not discuss robots.txt handling or failure modes, but those are partly covered by parameter schema.

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-structured with a clear purpose statement, explicit usage sections, a pagination note, and concise examples. Every section earns its place and the most important information is front-loaded.

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?

For an 8-parameter tool with an output schema, the description covers the core behavior, alternatives, pagination, and parameter usage. The output schema handles return values, so nothing essential is missing for correct invocation.

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 coverage is 100%, so the baseline is 3. The description adds practical meaning with examples showing max_length to save context and include_tables to preserve tabular data, plus pagination usage. This goes slightly beyond the raw 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?

States a specific verb and resource: fetch a single webpage and extract main content as clean markdown. Clearly differentiates from fetch_batch and discover_links, so an agent can select it without opening the schema.

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?

Provides explicit USE THIS WHEN and DO NOT USE WHEN sections, naming fetch_batch and discover_links as alternatives with reasons. This gives the agent unambiguous selection criteria.

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

Deploy Server