Skip to main content
Glama

Searchapi

by io.searchapi
OverviewDiscussionsAdmin

Google Ai Mode

google_ai_mode
Read-only

Get Google's AI-generated responses (AI Overviews) with source citations and reference links.

Two ways to call:

  • Text search — requires q.

  • Image analysis — requires url; optionally include q to ask a question about the image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch query for AI-generated response. Required if url not provided. Cannot exceed 8193 characters.
urlNoPublic image URL. Required if q not provided. Include q to ask a specific question about the image.
locationNoGeographic location for localized results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url
      Added value: +{
+  "description": "Public image URL. Required if q not provided. Include q to ask a specific question about the image.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Search query for AI-generated response. Required if url not provided."New value: +"Search query for AI-generated response. Required if url not provided. Cannot exceed 8193 characters."
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish readOnlyHint, openWorldHint, and destructiveHint false, so the description does not need to restate safety. It adds value by disclosing that output includes citations and reference links and that image analysis is a distinct behavior requiring a public URL.

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?

The description is short, front-loaded with the high-level purpose, and formats the two call modes with minimal prose. Every sentence contributes usable information with no filler.

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 tool with only three string parameters, full schema coverage, no nested objects, and no output schema, the description covers the key behavioral differences between text and image calls. The annotation cluster handles safety, and the description confirms the output expectation of citations and links.

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%, and the description mostly restates the conditional requirements already present in the schema (q vs url). The 'text search' and 'image analysis' framing helps organize the parameters, but it does not add new meaning about location, constraints, or output interpretation beyond what the schema already provides.

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?

The description begins with a specific action and resource: 'Get Google's AI-generated responses (AI Overviews) with source citations and reference links.' This clearly distinguishes it from sibling search tools like google_search_light or google_images_light, which do not provide AI Overviews.

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

Usage Guidelines4/5

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

The two calling modes are explicitly laid out with their parameter requirements: text search requires q, and image analysis requires url with optional q. This gives clear operating context, though it does not explicitly name alternatives or exclusion cases relative to sibling tools.

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

All Searchapi toolsInspect
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.

Resources