Skip to main content
Glama
Sign In

Oxylabs

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Oxylabs Scrape

oxylabs_scrape
Read-onlyIdempotent

Scrape any URL via the Oxylabs Web Scraper API (rotating proxies, anti-bot handling) and return the page HTML with its upstream status code. Set render_js:true to load the page in a headless browser first — use for JS-heavy sites. Calls are synchronous proxying and can take 10-30 seconds. BYOK: _apiKey is "username:password" from the Oxylabs dashboard. Example: oxylabs_scrape({ url: "https://example.com", _apiKey: "myuser:mypass" })

Input Schema

NameRequiredDescriptionDefault
urlYesThe absolute URL to scrape, e.g. "https://example.com/products"
_apiKeyYesOxylabs API credentials as "username:password" from the Oxylabs dashboard (https://dashboard.oxylabs.io). Free trial includes up to 2K results.
render_jsNoWhen true, render the page in a headless browser (executes JavaScript) before returning HTML. Use for JS-heavy sites. Default false (faster raw fetch).
geo_locationNoGeo location to proxy the request from, e.g. "United States" or "Germany". Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-oxylabs-username:your-oxylabs-password",
+    "url": "https://example.com/products"
+  },
+  {
+    "_apiKey": "your-oxylabs-username:your-oxylabs-password",
+    "geo_location": "United States",
+    "render_js": true,
+    "url": "https://example.com/dynamic-content"
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description adds significant behavioral context beyond annotations: rotating proxies, anti-bot handling, synchronous nature, time estimate, and authentication details (BYOK). Annotations already indicate readOnly, idempotent, and non-destructive, and the description aligns with and expands upon them.

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 concise: three sentences that front-load the core action and key details, followed by a practical example. Every sentence adds value with no redundancy.

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 no output schema, the description explicitly states it returns 'page HTML with its upstream status code'. It covers all parameters, authentication, behavior (render_js, timing), and provides an example, making it complete for an agent to use.

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?

Schema coverage is 100%, meeting baseline. The description adds value by clarifying the purpose of render_js (for JS-heavy sites) and specifying that _apiKey is 'username:password' from the Oxylabs dashboard. The example further aids understanding.

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 scrapes any URL via the Oxylabs Web Scraper API, returning HTML and status code. It distinguishes from siblings like oxylabs_amazon_product and oxylabs_google_search by being a general-purpose scraper.

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?

The description provides clear usage guidance, such as setting render_js:true for JS-heavy sites and noting that calls are synchronous and take 10-30 seconds. However, it does not explicitly mention when to not use this tool or suggest specific alternatives from the sibling list.

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

All Oxylabs toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources