Skip to main content
Glama
ScrapeOps

ScrapeOps MCP Server

by ScrapeOps

return_links

Extract and categorize all URLs from a webpage into pages and assets, enabling link analysis and sitemap generation.

Instructions

Extract and categorize all URLs from a webpage.

Best for:

  • Discovering all links on a page

  • Building sitemaps

  • Finding all assets (images, scripts, stylesheets)

  • Web crawling and link analysis

  • Identifying internal vs external links

What it extracts:

  • Links from , tags

  • Images from ,

  • Scripts from

  • Stylesheets from

  • Media from , ,

  • Embedded content from , ,

  • URLs from CSS url() functions

  • Meta refresh redirects

  • Open Graph and meta image URLs

URL Processing:

  • Converts relative URLs to absolute

  • Removes duplicates

  • Filters out mailto:, tel:, javascript:, data: URLs

  • Categorizes into pages vs assets

Returns: JSON with two arrays:

  • pages: HTML documents and navigational URLs

  • assets: Static resources (js, css, images, fonts, media)

Usage Examples:

  1. Basic URL extraction:

{
  "name": "return_links",
  "arguments": {
    "url": "https://example.com"
  }
}
  1. Extract URLs from protected site:

{
  "name": "return_links",
  "arguments": {
    "url": "https://protected-site.com",
    "bypass_level": "generic_level_1"
  }
}
  1. Geo-targeted extraction:

{
  "name": "return_links",
  "arguments": {
    "url": "https://example.de",
    "country": "de"
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
mobileNo
countryNo
premiumNo
residentialNo
bypass_levelNo
session_numberNo
max_request_costNo
optimize_requestNo
Behavior5/5

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

With no annotations, the description fully carries the burden. It details URL processing (relative to absolute, dedup, filtering), categorization into pages vs assets, and the JSON output structure. Example usage clarifies parameter behavior for bypass_level and country.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with sections (Best for, What it extracts, URL Processing, Returns, Usage Examples). It is longer than necessary but front-loads key information and uses clear formatting.

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 tool with 9 parameters, no output schema, and no annotations, the description covers functionality, output structure, and processing well. However, it lacks error handling, rate limit info, and full parameter descriptions, leaving some gaps.

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

Parameters2/5

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

Schema coverage is 0% (no parameter descriptions in schema). The description only provides examples for url, bypass_level, and country, leaving 6 undocumented parameters (mobile, premium, residential, etc.) unexplained. This fails to compensate for the lack of schema documentation.

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 it extracts and categorizes URLs from a webpage. It lists specific elements (links, images, scripts, etc.) and processing steps. Sibling tools (maps_web, extract_data) are distinct in purpose, so no ambiguity.

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 a 'Best for' section listing use cases like discovering links, building sitemaps, web crawling. It gives clear context for when to use, but does not explicitly state when not to use or compare to siblings. Lacks exclusion criteria.

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/ScrapeOps/scrapeops-mcp-server'

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