Skip to main content
Glama
Sign In

Oxylabs

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Oxylabs Amazon Product

oxylabs_amazon_product
Read-onlyIdempotent

Fetch structured Amazon product data by ASIN via the Oxylabs Web Scraper API — Amazon structured scraping: title, price, currency, rating, reviews count, stock/availability. Calls are synchronous proxying and can take 10-30 seconds. BYOK: _apiKey is "username:password" from the Oxylabs dashboard. Example: oxylabs_amazon_product({ asin: "B08N5WRWNW", domain: "com", _apiKey: "myuser:mypass" })

Input Schema

NameRequiredDescriptionDefault
asinYesThe Amazon product ASIN (10-character ID), e.g. "B08N5WRWNW"
domainNoAmazon marketplace domain suffix: "com" (default), "co.uk", "de", "co.jp", etc.
_apiKeyYesOxylabs API credentials as "username:password" from the Oxylabs dashboard (https://dashboard.oxylabs.io). Free trial includes up to 2K results.

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",
+    "asin": "B08N5WRWNW"
+  },
+  {
+    "_apiKey": "your-oxylabs-username:your-oxylabs-password",
+    "asin": "B08N5WRWNW",
+    "domain": "co.uk"
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable context: synchronous proxying, 10-30 second delay, and details about returned fields (title, price, currency, etc.), going beyond 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 a single dense paragraph that front-loads the purpose, then covers details, latency, and configuration. Every sentence is meaningful and concise, 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?

Given the tool has 3 parameters, no output schema, and no nested objects, the description is complete: it explains input, output fields, authentication, latency, and provides an example. No missing critical information.

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%, so baseline is 3. The description adds context beyond schema by explaining that '_apiKey' must be 'username:password' from Oxylabs dashboard and that 'domain' defaults to 'com'. It also provides an example call.

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 uses a specific verb 'Fetch structured Amazon product data by ASIN' and clearly identifies the resource (Amazon product via Oxylabs API). It distinguishes from sibling tools like 'oxylabs_google_search' by focusing on Amazon product data.

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 context: synchronous calls with 10-30 second latency, API key format, and an example. However, it does not explicitly state when to use this tool over alternatives or when not to use it.

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