Skip to main content
Glama

google_immersive_product

Scrapes Google's immersive product popup to retrieve brand info, price range, and store listings with ratings and reviews.

Instructions

Scrapes Google's immersive product popup view for a specific product, returning brand info, price range, and per-store listings with ratings and reviews. [Credits: Not specified in documentation] Notes: Seller pagination is manual: enable stores=true and increment sori by the cumulative count of sellers already returned across previous calls. Returns: { title, brand, reviews, rating, price_range, stores: [{name, link, price, ratings, reviews}] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
soriNoUsed with `stores` to fetch the next page of seller results. Its value depends on how many sellers were returned in prior responses; e.g. if the last two responses each returned 5 sellers, set sori=10 to continue.
storesNoEnables pagination to fetch more sellers. Pass true to enable. Must be used together with `sori`. (default: false)
countryNoTwo-letter country code for the Google search (e.g. US, UK, FR). (default: us)
languageNoLanguage of the results, e.g. en, es, fr, de. (default: en)
page_tokenYesToken required to display additional product details in Google's immersive popup. Typically obtained from a google_shopping response's scrapingdog_immersive_product_link.
Behavior3/5

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

No annotations provided, so description must carry burden. Discloses return structure and pagination behavior but does not mention rate limits, authentication, or side effects (though read-only assumed).

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?

Two substantive sentences plus return format. Front-loaded with purpose. Extraneous credit note but overall concise.

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?

Completeness is high given 5 parameters and pagination complexity. Covers pagination, parameter usage, return structure. No output schema, so return format is helpful.

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% with descriptions for all 5 parameters. Description adds context: explains sori and stores collaboration, and source of page_token. Also gives return format.

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 scrapes Google's immersive product popup view for a specific product, returning brand info, price range, and per-store listings. Distinguishes from sibling google_shopping by focusing on popup view.

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?

Provides explicit pagination guidance: enable `stores=true` and increment `sori` by cumulative sellers. Notes that page_token comes from google_shopping. Lacks explicit alternatives or when-not-to-use.

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