Skip to main content
Glama
praveenc

FetchV2 MCP Server

by praveenc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

discover_links

Extract all links from a webpage, optionally filtering by regex pattern, to build a targeted URL list for batch fetching.

Instructions

Discover all links on a webpage. Use this BEFORE fetch_batch to find relevant URLs.

USE THIS TOOL WHEN:

  • Exploring a documentation site to find relevant pages

  • Building a list of URLs to fetch in batch

  • Finding all subpages under a section (e.g., all /api/ docs)

  • Checking what content exists before deciding what to read

RECOMMENDED WORKFLOW:

  1. discover_links(url="https://docs.example.com/", filter_pattern="/guide/")

  2. Review the returned links and select relevant ones

  3. fetch_batch(urls=[selected_urls], max_length_per_url=1500)

FILTER EXAMPLES:

  • filter_pattern="/docs/" → Only links containing '/docs/'

  • filter_pattern="getting-started|quickstart" → Links with either term

  • filter_pattern=".md$" → Only markdown file links

NOTES:

  • Returns up to 100 links (more are noted but omitted to save context)

  • Relative URLs are automatically resolved to absolute URLs

  • JavaScript/mailto/anchor links are excluded

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe webpage URL to scan for links (e.g., a docs index or sitemap)
filter_patternNoRegex to filter links. Examples: '/docs/', '\.pdf$', 'api|guide'. Leave empty for all links.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Even though no annotations are provided, the description clearly discloses key behaviors: it returns up to 100 links, omits but notes extra links, resolves relative URLs to absolute, and excludes JavaScript/mailto/anchor links. These details help agents anticipate filtering and output shape without relying on annotations.

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?

The description is well structured with clear sections: purpose, when to use, workflow, filter examples, and notes. Every section adds practical information and is front-loaded with the core purpose before moving into examples.

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 a tool with only two optional/required parameters, an output schema, and a clear niche among siblings, this description covers usage context, limitations, filter syntax, and workflow integration. Nothing important 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?

The schema already has 100% description coverage for both parameters, so the baseline is 3. The description adds value by giving concrete filter_pattern examples and explaining how relative URLs are resolved, which clarifies effective use beyond basic schema definitions.

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 clear verb and resource: discover all links on a webpage. It also positions the tool relative to siblings by explicitly saying to use it BEFORE fetch_batch, distinguishing it from fetch variants. The workflow and usage conditions make its purpose unmistakable.

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 TOOL WHEN' bullets and a recommended 3-step workflow, including example calls with both parameters. It also mentions when to use at least one sibling (fetch_batch) after discovery, giving agents concrete decision criteria.

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