cloro

Scrape Google AI Mode

scrape_google_ai_mode

Read-only

Submit a prompt to Google AI Mode from a chosen country and return the AI answer with cited sources. Supports location or UULE targeting and desktop/mobile emulation. Costs 6 credits (4 base + 2 sync surcharge).

Input Schema

Name	Required	Description	Default
`gl`	No	ISO 3166-1 alpha-2 code for the result geography, sent to Google as gl (e.g. "us"). Use list_countries to see supported codes per model.
`hl`	No	Optional Google interface-language code, sent as hl (e.g. "de", "pt-br"). Defaults to the language derived from gl — set it when the geography's dominant language is not the one you want.
`uule`	No	Optional Google UULE location parameter. Mutually exclusive with location.
`device`	No	Device type to emulate. Defaults to desktop.	desktop
`prompt`	Yes	The prompt to submit to Google AI Mode.
`country`	No	ISO 3166-1 alpha-2 country code to geo-target the request from (e.g. "US"). Use list_countries to see supported codes per model. Deprecated — use gl instead; country is kept for compatibility and must not disagree with gl.
`include`	No	Optional flags for heavier payload fields, each off by default: markdown (the answer rendered as markdown), html (the answer page HTML). Leave unset for the leanest response.
`location`	No	Optional location name to target search results (e.g. "Austin, Texas, United States"). Mutually exclusive with uule.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / include / description

Previous value: -"Optional flags for heavier payload fields, each off by default: markdown (the answer rendered as markdown), html (the answer page HTML), rawResponse (the engine's unprocessed response payload). Leave unset for the leanest response."New value: +"Optional flags for heavier payload fields, each off by default: markdown (the answer rendered as markdown), html (the answer page HTML). Leave unset for the leanest response."

Changed1 schema field changedSep 8, 2026
- removedInput schema / properties / include / properties / googleGoto
```
Removed value: -{
-  "type": "boolean"
-}
```

Changed1 schema field changedSep 2, 2026

changedInput schema / properties / include / description

Previous value: -"Optional flags to include heavier payload fields in the response. Leave unset for the leanest response."New value: +"Optional flags for heavier payload fields, each off by default: markdown (the answer rendered as markdown), html (the answer page HTML), rawResponse (the engine's unprocessed response payload). Leave unset for the leanest response."

Changed1 schema field changedAug 31, 2026
- addedInput schema / properties / include / properties / googleGoto
```
Added value: +{
+  "type": "boolean"
+}
```

Changed4 schema fields changedAug 25, 2026

changedInput schema / properties / country / description

Previous value: -"ISO 3166-1 alpha-2 country code to geo-target the request from (e.g. \"US\"). Use list_countries to see supported codes per model."New value: +"ISO 3166-1 alpha-2 country code to geo-target the request from (e.g. \"US\"). Use list_countries to see supported codes per model. Deprecated — use gl instead; country is kept for compatibility and must not disagree with gl."

addedInput schema / properties / gl

Added value: +{
+  "description": "ISO 3166-1 alpha-2 code for the result geography, sent to Google as gl (e.g. \"us\"). Use list_countries to see supported codes per model.",
+  "type": "string"
+}

addedInput schema / properties / hl

Added value: +{
+  "description": "Optional Google interface-language code, sent as hl (e.g. \"de\", \"pt-br\"). Defaults to the language derived from gl — set it when the geography's dominant language is not the one you want.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "prompt",
-  "country"
-]New value: +[
+  "prompt"
+]

First observedAug 24, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, destructiveHint=false), yet the description adds genuinely new context: the credit cost breakdown ('6 credits (4 base + 2 sync surcharge)') and the fact that this is a synchronous, cost-bearing call. It stops short of disclosing latency, rate limits, or failure behavior, but the cost disclosure is meaningful value beyond structured fields.

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?

Three short sentences, front-loaded with the core action before capabilities and cost. Each sentence carries distinct information with no repetition, though the cost sentence could be positioned later without loss.

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 an 8-parameter tool with a nested object and no output schema, the description conveys the action, the response shape at a high level ('AI answer with cited sources'), targeting options, and cost. The heavy parameter detail is fully carried by the 100%-covered schema, leaving only minor gaps around response payload nuances.

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 every parameter including the nested 'include' flags and the deprecated 'country' is already documented in the schema. The description echoes the targeting and device capabilities but adds no syntax or format detail beyond what the schema provides, making baseline 3 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 verb and resource — 'Submit a prompt to Google AI Mode' — and names the returned payload ('the AI answer with cited sources'), which clearly separates it from scrape_google or scrape_google_news. It never explicitly contrasts itself with the sibling scraping tools, though the target engine is unambiguous.

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 implies usage through capability statements ('Supports location or UULE targeting and desktop/mobile emulation'), but gives no explicit when-to-use condition versus scrape_google or scrape_gemini, and no guidance on prerequisites such as looking up valid country codes.

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

All cloro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Scrape Google AI Mode

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources