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.

To ask a follow-up, pass the conversation_token from the previous response along with the next question in q. The answer then keeps the context of the earlier turns.

Input Schema

NameRequiredDescriptionDefault
qNoSearch query for AI-generated response. Required if url not provided. Cannot exceed 8193 characters, fewer with url for non-Latin text.
urlNoPublic image URL. Required if q not provided. Include q to ask a specific question about the image.
locationNoGeographic location for localized results.
conversation_tokenNoContinues a previous conversation. Pass the pagination.conversation_token returned by the last response together with the follow-up question in q. Omit it to start a new conversation. Cannot be combined with url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Search query for AI-generated response. Required if url not provided. Cannot exceed 8193 characters."New value: +"Search query for AI-generated response. Required if url not provided. Cannot exceed 8193 characters, fewer with url for non-Latin text."
  2. Changed1 schema field changed
    • addedInput schema / properties / conversation_token
      Added value: +{
+  "description": "Continues a previous conversation. Pass the pagination.conversation_token returned by the last response together with the follow-up question in q. Omit it to start a new conversation. Cannot be combined with url.",
+  "type": "string"
+}
  3. 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"
+}
  4. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  5. 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."
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world behavior. The description adds useful behavioral context beyond that: responses include source citations and reference links, and conversation_token preserves prior-turn context. It does not address rate limits or failure modes, but it meaningfully supplements the annotations.

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 front-loaded with the core purpose, then organized into clear call modes and follow-up behavior. Every sentence contributes directly to correct invocation, with no filler.

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 four-parameter tool with no output schema and rich annotations, the description covers the essential calling patterns and follow-up behavior. It could add a bit more about error handling or constraints, but nothing critical for correct invocation is missing.

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 coverage is 100%, so the baseline is 3, but the description adds synthesis beyond individual field descriptions: it groups q and url into distinct call modes and explains that conversation_token is used with a follow-up question in q. That combination guidance is useful and not fully redundant.

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?

The description states a specific verb and resource: 'Get Google's AI-generated responses (AI Overviews) with source citations and reference links.' This distinguishes it from ordinary search siblings such as google_search_light, though it does not explicitly name them or state exclusions.

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?

It clearly explains two invocation modes — text search requiring q and image analysis requiring url — and explains how to continue a conversation. It does not compare against sibling alternatives like google_lens or google_search_light, so it is clear but lacks explicit alternative routing.

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
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources