Skip to main content
Glama

MagicGEO — AI Search & Commerce Agent Seller

Search Seller Agent catalogs

search_catalog
Read-onlyIdempotent

Search products in Shopify stores that enabled MagicGEO Seller Agent, by keywords matched against title, vendor, product type, tags and keywords. Returns store domain, numeric product_id, title, vendor, product URL and the last synced availability with its sync time. It never returns a price or a live offer: call verify_agent_offer with the returned shop and product_id to read live price and availability and obtain a native checkout link.

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": {
      "query": "<query>"
    },
    "name": "search_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
shopNoRestrict to one store domain, e.g. example.myshopify.com
limitNoMaximum results, 1-20 (default 10)
queryYesSearch terms, e.g. snowboard
in_stock_onlyNoOnly products available at the last catalog sync (still verify live)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With readOnlyHint/idempotentHint already covering safety, the description adds real behavioral context the annotations cannot: the returned field set, the fact that availability is from the last catalog sync rather than live, and the two-step search-then-verify workflow. It also discloses a meaningful limitation (no prices, no live offers) that would otherwise cause silent misuse.

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?

Three sentences, front-loaded with the core action, then the return contract, then the hand-off to the sibling tool. Every sentence carries distinct information; nothing is restated from the schema or annotations.

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 four-parameter read-only search with no output schema, the description covers purpose, matching semantics, return fields, staleness caveats, and the follow-up call. An agent has everything needed to invoke it correctly and interpret results.

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. The description earns above baseline by explaining what the required `query` actually matches against (title, vendor, product type, tags, keywords) and by reinforcing that `in_stock_only` reflects sync-time state that still needs live verification.

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?

States a specific verb and resource ('Search products in Shopify stores that enabled MagicGEO Seller Agent') plus the exact matching fields (title, vendor, product type, tags, keywords). It also explicitly separates itself from the sibling verify_agent_offer, so an agent can choose between them without opening either schema.

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?

Gives an explicit when-to-use-next rule: this tool never returns price or a live offer, so call verify_agent_offer with the returned shop and product_id. That names the alternative and the condition that selects it, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources