Fudge for Shopify

Get search results

get_search_results

Read-onlyIdempotent

Read Google’s live first results page for one search in one country: ranked results, features, AI Overview citations, People Also Ask and related searches. Changes nothing and uses no credits; each store has a daily limit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "location": "<location>",
      "keyword": "<keyword>"
    },
    "name": "get_search_results"
  }
}

Input Schema

Name	Required	Description	Default
`store`	No	The connected store to use. Omit when only one is connected.
`device`	No		mobile
`keyword`	Yes
`language`	No	Language code, e.g. "en". Defaults to the store’s language.
`location`	Yes	Target country, e.g. "United States". Ask the merchant which countries they sell to if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds meaningful context beyond that: 'Changes nothing and uses no credits; each store has a daily limit' discloses cost and a per-store rate ceiling.

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?

A single front-loaded sentence that leads with the operation and follows with return contents and cost constraints. No redundant or filler wording.

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?

There is no output schema, and the description compensates by listing the returned data categories, plus credit and daily-limit behavior. Minor gaps remain around failure modes and result depth, but an agent has enough to call it correctly.

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?

With 60% schema description coverage, the schema already explains store, language and location. The description only reinforces the one-search/one-country framing for keyword and location and adds nothing about device, language defaults, or store selection.

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 names a specific verb and resource ('Read Google’s live first results page') and enumerates exactly what comes back: ranked results, features, AI Overview citations, People Also Ask and related searches. This clearly separates it from sibling tools such as get_keyword_metrics or check_page.

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?

It scopes usage to 'one search in one country', implying when this tool applies, but never states when to prefer it over alternatives or when to avoid it. The daily-limit note hints at a constraint but is not framed as usage guidance.

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

All Fudge for Shopify 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.