Skip to main content
Glama

google_ai_overview

Retrieve Google AI Overview results by using the follow-up URL provided in a Google Search API response, returning structured text blocks and references.

Instructions

Fetches Google AI Overview results using the follow-up url returned inside a Google Search API response, for cases where Google requires a separate request to load the AI Overview content. [Credits: 5 API credits per successful request] Notes: This endpoint is only used when the primary Google Search API response indicates AI Overview content requires a secondary fetch (i.e., it returns a url for it rather than inline content). The url value is single-use and time-limited to 2 minutes from issuance. Returns: JSON with ai_overview object containing text_blocks (array of typed blocks: paragraph {type, snippet, snippet_highlighted_words}, list {type, list: [{snippet}]}) and references (array of {title, link, snippet, source, index}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe AI Overview fetch URL returned by the Google Search API response's ai_overview field. Expires after 2 minutes.
Behavior4/5

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

Discloses cost, single-use and time-limited nature, and return format. No annotations provided, so description carries full burden. Missing failure modes for expired URLs.

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 sentences plus concise notes on credits and output. Front-loaded with purpose, minimal waste.

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?

Given single parameter and no output schema, description details when, why, how, cost, limitations, and expected JSON structure. Very complete.

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

Parameters4/5

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

Schema has 100% coverage with a description. Description adds context about the URL source and expiration, enhancing understanding beyond schema.

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?

Description clearly states it fetches Google AI Overview using a follow-up URL from Google Search API. Distinguishes from sibling tools like 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 Guidelines5/5

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

Explicitly states when to use (only when primary response indicates secondary fetch), notes URL is single-use and time-limited (2 minutes), and provides credit cost.

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/alessandrobenigni/ScrapingDog-MCP'

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