Skip to main content
Glama
Sign In

Oxylabs

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Oxylabs Google Search

oxylabs_google_search
Read-onlyIdempotent

Run a Google search through the Oxylabs Web Scraper API and return structured organic results (position, title, url, description) — Google structured scraping with geo-targeting. Calls are synchronous proxying and can take 10-30 seconds. BYOK: _apiKey is "username:password" from the Oxylabs dashboard. Example: oxylabs_google_search({ query: "best espresso machine", geo_location: "United States", _apiKey: "myuser:mypass" })

Input Schema

NameRequiredDescriptionDefault
pagesNoNumber of result pages to fetch. Default 1.
queryYesThe Google search query, e.g. "best espresso machine 2026"
_apiKeyYesOxylabs API credentials as "username:password" from the Oxylabs dashboard (https://dashboard.oxylabs.io). Free trial includes up to 2K results.
geo_locationNoGeo location for localized results, e.g. "United States", "London,England,United Kingdom". 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",
+    "query": "best espresso machine 2026"
+  },
+  {
+    "_apiKey": "your-oxylabs-username:your-oxylabs-password",
+    "geo_location": "London,England,United Kingdom",
+    "pages": 2,
+    "query": "restaurants near me"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/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 latency, and API key format. No contradictions.

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 two concise sentences plus a tip and example. It front-loads the core function and avoids unnecessary details, making it easy to scan.

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?

Despite no output schema, the description specifies the return format (structured organic results with position, title, url, description). It covers input, behavior, and output sufficiently for a search 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?

Schema coverage is 100%, but the description adds meaning by explaining the API key format (username:password) and providing an example call. It also clarifies the optional geo_location parameter's purpose for localized results.

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 that the tool runs a Google search through Oxylabs Web Scraper API and returns structured organic results with specific fields (position, title, url, description). It also mentions geo-targeting, which differentiates it from sibling tools like oxylabs_amazon_product.

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 explains when to use the tool (for Google search with geo-targeting), includes an example, and notes that calls take 10-30 seconds. It does not explicitly state when not to use it or compare to siblings, but the name and context imply its specific use case.

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