Skip to main content
Glama

Google search results

get_google_search_results
Read-only

This is a FALLBACK tool — use fast_search first for general web searches. Only use this tool when you need specialized search types that fast_search does not support: news, maps, Google Lens, shopping, image search, or Google AI mode.

Scrape Google search results using ScrapingBee and return the results. This tool can scrape normal results, news results, maps results, search using google lens, shopping related results, image results, and get the result from Google's AI mode. It can even return the HTML along with the search results.

Scope: one query per call. To run many queries in one pass, or to write results to disk instead of into the conversation, use the ScrapingBee CLI — scrapingbee <command> --input-file queries.txt --output-dir results.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "search": "<search>"
    },
    "name": "get_google_search_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoResponse-header label only.
nfprNoWhether to disable Google's autocorrection feature or not.
pageNoThe page number to return.
pagesNoNumber of pages to aggregate (max 10, default 1).
deviceNoThe device to use for the search (desktop, mobile).desktop
radiusNoRadius in meters (requires latitude and longitude).
searchYesThe search query to use.
sort_byNoShopping sort order: relevance, reviews, price_asc, price_desc.
add_htmlNoWhether to return the HTML along with the search results.
languageNoThe language to use for the search (Example: en, fr, de, etc.).en
latitudeNoLatitude in decimal degrees for geographic searches.
longitudeNoLongitude in decimal degrees for geographic searches.
max_priceNoShopping maximum price filter.
min_priceNoShopping minimum price filter.
date_rangeNoFilter by date range: past_hour, past_day, past_week, past_month, past_year. Only for classic, news, and images.
search_typeNoThe search type to use (classic: normal results, news: news results [not available if device is mobile], maps: maps results, lens: search using google lens [requires image url as search parameter], shopping: shopping related results, images: image results, ai_mode: get the result from Google's AI mode, ads: paid-ad results).classic
country_codeNoThe country code to use for the search (Example: us, fr, de, etc.).us
extra_paramsNoExtra parameters to pass to the search (Example: tbs=qdr:d&udm=7).
light_requestNoWhether to use a light request or not.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety profile is covered; the description usefully adds that results come from a third party (ScrapingBee), that HTML can be returned alongside results, and that one query is handled per call. It omits cost/credit implications, rate limits, or failure modes for blocked scrapes, so it adds context but not full behavioral depth.

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?

The fallback warning and the fast_search routing are front-loaded ahead of the capability list, which is the right order. The capability enumeration is somewhat redundant with the search_type enum in the schema, costing a bit of length.

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 19-parameter scraping tool with annotations and an output schema, the description covers routing, scope limits, and the multi-type capability surface, and it delegates return-value detail to the output schema. Nothing an agent needs to choose or call it correctly is missing.

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 description coverage is 100%, so all 19 parameters are already documented, giving baseline 3. The description only adds the caveat that `search` must hold an image URL when search_type=lens and that add_html toggles the HTML payload, repeating what the schema already states.

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?

States specific verb+resource ('Scrape Google search results using ScrapingBee') and enumerates the supported search types (news, maps, Lens, shopping, images, ai_mode, ads, classic), which distinguishes it from the generic sibling fast_search.

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 names fast_search as the default and states the exact condition for escalating to this tool (specialized search types), plus an exclusion for bulk/many-query runs pointing to the ScrapingBee CLI. Both when-to-use and when-not are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources