Skip to main content
Glama
subimpact

subimpact-data-mcp

Official
by subimpact
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

google_ai_mode

Retrieve country- and language-specific AI Mode answers with full text, structured blocks, resolved source URLs, and per-paragraph citations for research and monitoring.

Instructions

Google AI Mode Scraper

Real Google AI Mode answers (udm=50 tab) rendered in Android Chrome, for any country and language: full answer, structured blocks, resolved source URLs and per-paragraph citations. From $0.0018 per answer ($0.003 on Free/Starter). Uncited answers are flagged; failed and empty queries are free.

Pricing (pay per event, billed to your Apify account): AI Mode search completed: $0.003; platform usage billed to your account.

Runs on Apify as subimpact/google-ai-mode-scraper.

Input Schema

NameRequiredDescriptionDefault
glNoTwo-letter country code for the market whose AI Mode answers you want, e.g. ae (UAE), my (Malaysia), sg (Singapore), id (Indonesia), au (Australia), us. Works on both backends.us
hlNoLanguage code for Google's interface and answer, e.g. en, ar, ms, id, zh-CN. Write your queries in the same language. In markets where English is not the main search language (e.g. id, th) use the local language: English queries there often get generic/US answers.en
udm50No[legacy http backend only] Appends udm=50. NOTE: the forced shell currently returns no answer browserlessly (Google requires a real browser for the folwr stream) — defaults OFF.
backendNoandroid (default) = real AI Mode tab (udm=50) rendered in Android Chrome: full answer, structured blocks, resolved source URLs. http = legacy browserless SERP fetch (only returns AI answers Google embeds in the classic results page; uses gl/hl/location/udm50/retry options below).android
queriesYesQueries to get Google AI Mode answers for. Each query is run on the real AI Mode tab (udm=50) in a real Android Chrome browser.
locationNoGoogle canonical location name, e.g. 'Dubai,Dubai,United Arab Emirates' or 'Kuala Lumpur,Federal Territory of Kuala Lumpur,Malaysia'. Leave empty to use the main city of the chosen country (Dubai, Kuala Lumpur, Singapore, Jakarta, Sydney, ...). Type none to send no location.
_maxItemsNoHow many dataset items to return to the model (1-1000, default 50). Truncates the response only; it does not change what the Actor collects or charges for.
skipCacheNoBy default, a question that was answered for the same country, language and location in the last hour may be served from our cache (marked cached: true, with cached_at). Turn this on to always fetch a fresh answer from Google, for example when tracking how answers change. Fresh answers take longer under heavy load.
concurrencyNoParallel queries (1-30). On the android backend this is capped automatically to the size of the browser pool.
_maxChargeUsdNoPer-run spending cap in USD (default 0.5). Passed to Apify as the run option maxTotalChargeUsd, so the run stops when it reaches this charge.
retryDeferredNo[legacy http backend only] When the answer is deferred, re-fetch through the folsrch async endpoint. ON by default (recovery rate ~90%).
captureRawHtmlNo[legacy http backend only] Save raw SERP HTML to the key-value store for every query (for corpus/debugging). Adds storage cost.
retryDeferredMaxFetchesNo[legacy http backend only] Upper bound on recovery fetches per query (1-5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose useful traits: pay-per-event pricing, billing to the Apify account, free failed and empty queries, uncited answers flagged, and real Android Chrome rendering. It does not cover authentication requirements or broader rate-limit behavior outside the schema.

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 description is front-loaded with what the tool returns and is mostly efficient. However, pricing is repeated twice ('From $0.0018 per answer...' and 'AI Mode search completed: $0.003'), and the 'Runs on Apify as...' line adds little for tool selection.

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?

Given 13 parameters, no annotations, and no output schema, the description covers the output shape (answer, structured blocks, citations), billing model, and key behavioral caveats like uncited flagging. It lacks explicit use-case routing versus siblings and auth details, but the rich schema compensates for most parameter gaps.

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 are already documented in the schema, including caching, concurrency caps, and spending limits. The description adds only high-level pricing context and no parameter-specific meaning beyond what the schema provides; baseline 3 is appropriate.

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 resource and output: real Google AI Mode answers from the udm=50 tab, including full answer, structured blocks, resolved source URLs, and per-paragraph citations. It clearly distinguishes itself from a generic search result, though it does not explicitly name or differentiate from sibling google_search.

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?

Usage is implied by 'for any country and language' and the emphasis on AI Mode-specific answers, but there is no explicit when-to-use guidance versus google_search or other siblings, nor any stated exclusions. The agent must infer that this is for AI Mode answers specifically.

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