Skip to main content
Glama
mcp-webfetch

mcp-webfetch

by Mahgal

extract_links

Fetch a web page and return its de-duplicated HTTP/HTTPS links as a JSON array.

Instructions

Fetch a web page and return the de-duplicated list of http/https links it contains, as a JSON array.

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": "extract_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe http(s) URL to inspect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the de-duplication behavior, the link scheme filter (http/https only), and the return shape, but says nothing about network access requirements, redirect handling, failure modes, or whether the page is rendered client-side.

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?

A single front-loaded sentence with the resource first and the output contract second; every clause earns its place and nothing is padded.

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 read tool, the description covers input intent and the return contract in lieu of an output schema. Only operational details such as error behavior and fetching constraints are absent, which is a minor gap at this complexity.

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?

Only one required parameter and the schema already documents it at 100% coverage, so the baseline is high. The description reinforces that the URL points at a web page to inspect, which matches the schema without adding contradicting meaning.

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?

Names a specific verb (fetch) and resource (web page) and states exactly what comes back: a de-duplicated JSON array of http/https links. It is clear what distinguishes it from a plain page-fetch sibling, though it never names or contrasts with fetch_url explicitly.

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?

The implied use case is evident (you want the links, not the page body), but there is no explicit when-to-use or when-not-to-use guidance and no mention of the fetch_url alternative that an agent would otherwise have to disambiguate on its own.

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