Skip to main content
Glama
oxylabs

Oxylabs MCP Server

Official

google_search_scraper

Read-only

Scrape Google search results with support for parsing, pagination, geolocation, and locale settings to extract structured data efficiently.

Instructions

Scrape Google Search results.

Supports content parsing, different user agent types, pagination, domain, geolocation, locale parameters and different output formats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to retrieve in each page.
pagesNoNumber of pages to retrieve.
parseNoShould result be parsed. If the result is not parsed, the output_format parameter is applied.
queryYesURL-encoded keyword to search for.
domainNo Domain localization for Google. Use country top level domains. For example: - 'co.uk' for United Kingdom - 'us' for United States - 'fr' for France
localeNo Set 'Accept-Language' header value which changes your Google search page web interface language. Examples: - 'en-US' for English, United States - 'de-AT' for German, Austria - 'fr-FR' for French, France
renderNo Whether a headless browser should be used to render the page. For example: - 'html' when browser is required to render the page.
ad_modeNoIf true will use the Google Ads source optimized for the paid ads.
start_pageNoStarting page number.
geo_locationNo The geographical location that the result should be adapted for. Use ISO-3166 country codes. Examples: - 'California, United States' - 'Mexico' - 'US' for United States - 'DE' for Germany - 'FR' for France
output_formatNo The format of the output. Works only when parse parameter is false. - links - Most efficient when the goal is navigation or finding specific URLs. Use this first when you need to locate a specific page within a website. - md - Best for extracting and reading visible content once you've found the right page. Use this to get structured content that's easy to read and process. - html - Should be used sparingly only when you need the raw HTML structure, JavaScript code, or styling information.
user_agent_typeNoDevice type and browser that will be used to determine User-Agent header value.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already provide readOnlyHint=true, so the description is consistent. It adds no additional behavioral traits (e.g., rate limits, permissions, side effects) beyond listing parameters. It does not contradict 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 two sentences: purpose first, then feature list. No wasted words, efficient and front-loaded. Ideal for quick comprehension.

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 12 parameters and output schema, the description provides a high-level overview covering major capabilities. It could mention interaction between parameters or typical usage flow, but the schema and output schema fill details. Adequate for complexity.

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

Parameters3/5

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

Schema coverage is 100%, meaning all parameters are documented in the input schema. The tool description lists parameter categories but adds no new meaning beyond the schema descriptions. Baseline met.

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 'Scrape Google Search results' with a specific verb and resource. It lists supported features (parsing, pagination, domain, etc.) that differentiate it from siblings like amazon_product_scraper and universal_scraper. No confusion about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool or when to avoid it. It only lists features, implying usage for Google Search. Sibling names hint at different sources, but no direct comparison or exclusions are provided.

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/oxylabs/oxylabs-mcp'

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