Skip to main content
Glama
ScrapeOps

ScrapeOps MCP Server

by ScrapeOps

maps_web

Browse, scrape, and capture web pages with proxy rotation, JavaScript rendering, and anti-bot bypass.

Instructions

Browse and scrape any webpage with advanced proxy and rendering capabilities.

Best for:

  • Reading webpage content

  • Taking screenshots of websites

  • Verifying how a site looks from different countries

  • Bypassing anti-bot protections

  • Accessing JavaScript-rendered content

Key Features:

  • Geo-targeting: Access websites from different countries

  • JavaScript Rendering: Render SPAs and dynamic content

  • Residential/Mobile Proxies: Better success on challenging sites

  • Screenshots: Capture visual snapshots of pages

  • Anti-Bot Bypass: Multiple bypass levels for protected sites

  • Wait Controls: Wait for elements or time before capture

Usage Examples:

  1. Simple page browse:

{
  "name": "maps_web",
  "arguments": {
    "url": "https://example.com"
  }
}
  1. Screenshot for website:

{
  "name": "maps_web",
  "arguments": {
    "url": "https://example.de",
    "render_js": true,
    "json_response": true,
    "screenshot": true
  }
}
  1. Access Cloudflare-protected site:

{
  "name": "maps_web",
  "arguments": {
    "url": "https://protected-site.com",
    "bypass_level": "cloudflare_level_2",
    "residential": true,
    "render_js": true
  }
}
  1. Wait for dynamic content:

{
  "name": "maps_web",
  "arguments": {
    "url": "https://spa-app.com",
    "render_js": true,
    "wait_for": ".product-list",
    "wait": 2000
  }
}

Returns: HTML content, or JSON with screenshot (base64) if screenshot=true.

IMPORTANT - Default Behavior:

  • Always start with BASIC settings (just the URL)

  • Do NOT use advanced parameters (render_js, residential, bypass_level, premium) unless:

    1. The user explicitly requests them, OR

    2. A previous request failed AND the user gives permission to use them

If a request fails:

  • The error response will ask for permission to retry with advanced options

  • Wait for user confirmation before using advanced parameters

  • Never auto-enable advanced parameters without user consent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
waitNo
mobileNo
scrollNo
countryNo
premiumNo
wait_forNo
render_jsNo
screenshotNo
device_typeNo
residentialNo
bypass_levelNo
keep_headersNo
session_numberNo
follow_redirectsNo
max_request_costNo
optimize_requestNo
return_status_codesNo
Behavior4/5

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

No annotations, but description comprehensively explains capabilities (geo-targeting, anti-bot, screenshots, wait controls) and return format. Lacks mention of potential side effects like cookies or rate limits, but overall transparent.

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?

Well-structured with sections, bullet points, and code examples. Front-loads purpose and key features. Slightly long but every section adds value; no wasted words.

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?

With 18 parameters and no output schema, description provides thorough context: best-for, features, examples, default behavior, error handling, and return format. Missing explanations for a few parameters, but overall complete for a complex tool.

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?

With 0% schema description coverage, baseline is 4. Description explains many parameters via key features and usage examples (e.g., wait, wait_for, screenshot, render_js, bypass_level, residential). Some parameters (keep_headers, session_number) not mentioned, but coverage is high enough to justify a 4.

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 the tool is for browsing and scraping webpages with advanced proxy and rendering capabilities. It distinguishes from sibling tools by listing specific features like geo-targeting and JavaScript rendering.

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?

Explicitly provides 'Best for' scenarios and 'IMPORTANT - Default Behavior' instructions on when to use advanced parameters, requiring user confirmation for retries. This gives clear guidance on appropriate usage.

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