Skip to main content
Glama
Sign In
Autom MCP Server

Autom MCP Server

Official
by automdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Google Search

google_search
Read-only

Run Google searches and retrieve structured SERP data with pagination, geo/language filters, and advanced query operators.

Instructions

Google Search. Scrape Google Search results via API and retrieve structured SERP data with pagination. Credit cost: 1 credit per call.

Input Schema

NameRequiredDescriptionDefault
crNoLimit results to one or more countries. Use country{XX} with | as delimiter (e.g. countryFR|countryDE).
glNoCountry to use for the Google search. Two-letter country code (e.g. us for the United States, uk for United Kingdom, or fr for France).
hlNoLanguage to use for the Google search. Two or three-letter language code (e.g. en, es, fr), optionally followed by a region code (e.g. en-gb, es-419).
lrNoLimit results to one or more languages. Use lang_{xx} with | as delimiter (e.g. lang_fr|lang_de).
numNoMaximum number of results to return per page (deprecated). Default: 10.
tbsNoAdvanced search filters string (e.g. time ranges: qdr:h last hour, qdr:d last day, qdr:w last week, qdr:m last month, qdr:y last year).
pageNoPage number / offset used for pagination. Default: 1.
safeNoAdult content filter. active enables Google SafeSearch; off disables it. Omit to use Google default.
uuleNoGoogle encoded location parameter. Use for precise geo targeting. Note: uule and location cannot be used together.
queryYesThe search query you want to run on Google (supports advanced operators like site:, inurl:, intitle:).
fieldsNoComma-separated list of fields to keep in the response, with dot notation for nested fields (e.g. name,location.city). Does not change the credit cost.
locationNoHuman-readable location to originate the search from (e.g. New York, NY, Paris, France). If several locations match, the most popular one is used. Note: location and uule cannot be used together.
google_domainNoGoogle domain to use for the search. Defaults to google.com. Default: "google.com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and non-destructive, so safety is covered. The description adds genuinely useful operational facts that annotations cannot express: a cost of 1 credit per call and the availability of pagination. It stops short of rate limits, per-page caps, or what triggers failure, which matters for a paid open-world call.

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?

Two short sentences, zero filler, with the core action first and cost/pagination compactly appended. Nothing to cut.

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?

For a 13-parameter read-only search tool whose params are fully documented in the schema and which has no output schema, the description covers action, data shape in outline, pagination and cost. The missing piece is sibling differentiation and any hint of the SERP response shape beyond 'structured SERP data'.

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 13 parameters, including the uule/location mutual exclusion and the deprecated num, are already documented in the schema. The description adds no parameter meaning beyond that, which is the baseline case when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: scrape Google Search results and return structured SERP data with pagination. Clear what it does, but it never distinguishes itself from near-neighbors like google_search_light, google_search_ai, or brave_search/duckduckgo_search, so an agent cannot route on description alone.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance at all. It mentions pagination exists but never says to use it instead of google_search_light, or when Google is the right engine versus bing_search or duckduckgo_search, all of which are siblings.

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

Deploy Server

Other Tools