Skip to main content
Glama
mcp-webfetch

mcp-webfetch

by Mahgal

fetch_url

Fetch any HTTP/HTTPS web page and convert its HTML into clean Markdown with headings, paragraphs, and links preserved. Enforces a 10-second timeout and rejects non-HTML or oversized responses.

Instructions

Fetch a web page and return its content as clean Markdown (title, headings, paragraphs and links preserved). Times out after 10s and rejects non-HTML or oversized responses.

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_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe http(s) URL to fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a fair job: it discloses a 10s timeout and that non-HTML or oversized responses are rejected, which are real failure modes an agent must plan for. It also describes the output shape (title, headings, paragraphs, links preserved), though it is silent on redirects, auth, rate limits, and JS rendering.

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?

Two tight clauses, output format first and limits second, with zero filler. Every phrase — Markdown, the preserved elements, the timeout, the rejected inputs — carries information the agent needs.

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?

For a one-parameter fetch tool with no output schema, the definition covers return format and key failure modes, which is enough to call it correctly. The remaining gaps (redirects, authentication, JS-rendered pages) are secondary but would matter for some URLs.

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

Parameters3/5

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

There is a single parameter with 100% schema description coverage ("The http(s) URL to fetch"), so the schema already does the work. The description adds no constraints beyond the http(s) requirement, so the baseline of 3 applies.

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?

"Fetch a web page and return its content as clean Markdown" states a specific verb (fetch), resource (web page) and output form (Markdown), so the agent knows exactly what comes back. It does not distinguish itself from the sibling extract_links, leaving the boundary between a full-page fetch and link extraction unstated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the verb: use this when you need a page's readable content. There is no explicit when-not guidance, no mention of when to prefer extract_links, and no note about pages requiring JS or authentication.

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

Deploy Server

Other Tools