AI commerce for Shopify: product search, comparison, recommendations, and checkout via MCP.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 4.4/5 across 7 of 7 tools scored.
Most tools have distinct purposes with clear boundaries, such as search_products for browsing and skincare_recommend for personalized advice. However, create_checkout and skincare_cart both handle checkout functionality, which could cause confusion about when to use each, as they overlap in creating purchase links.
The naming is mixed with some tools using verb_noun patterns like compare_products and get_product, while others like skincare_cart and skincare_recommend use a noun-based prefix. This inconsistency is noticeable but still readable, as most names are descriptive of their functions.
With 7 tools, the count is well-scoped for an e-commerce and skincare recommendation server. Each tool serves a specific role, such as product lookup, comparison, checkout, and issue reporting, making the set comprehensive without being overwhelming.
The tool set covers key e-commerce workflows like searching, comparing, recommending, and purchasing products, with a useful issue reporting tool. A minor gap is the lack of tools for updating or managing user profiles or orders, but core shopping and recommendation tasks are well-supported.
compare_productsCompare two or more products side by side. Use when the user asks to compare, says 'X vs Y', or wants to decide between options. Do not use for single product lookup — use get_product instead. Returns structured comparison with shared attributes, differences, tradeoffs, and a decision hint.
| Name | Required | Description | Default |
|---|---|---|---|
| products | Yes | Product titles or SKUs to compare (e.g. ['MIRA', 'CryoSculpt']) |
create_checkoutInspectCreate a checkout URL for one or more products. Pass variant IDs (items) and/or product URLs (product_urls). When a product URL is provided (e.g. https://laluer.com/products/mira), the tool resolves it to a variant ID automatically — no catalog import needed. Supports discount codes, cart notes, and selling plans. Do not use unless the user wants to buy — use search_products or skincare_recommend first. Returns a direct Shopify checkout link the user can click to buy.
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Cart note visible to the merchant | |
| items | No | Products to add to cart by variant ID | |
| decision_id | No | Decision Check ID from a prior /validate call. Required when this merchant enforces authority-gated checkout (require_authority_for_checkout); ignored otherwise. | |
| product_urls | No | Products to add to cart by URL — resolved to variant IDs automatically | |
| discount_code | No | Discount code to apply (e.g. 'WELCOME10') |
get_productGet full details for a specific product by SKU or title. Use when the user asks about a specific product by name (e.g. 'tell me about MIRA', 'show me the serum'). Do not use for browsing or recommendations — use search_products or skincare_recommend. Returns a widget card with the product details, image, price, and checkout button.
| Name | Required | Description | Default |
|---|---|---|---|
| sku | No | Exact product SKU (e.g. 'LL-4632379916336') | |
| title | No | Product title to search for (fuzzy match) |
get_research_noteGet the summary and URL of a specific SearchShopAI Research Note by its slug (returned by search_research_notes).
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The note slug, e.g. 'the-ai-attribution-blind-spot' |
recommendGet a personalized product recommendation with domain-expert scoring, safety notes, and transaction authority. Use when the user wants advice, has a concern, or asks what to buy. Returns scored products with checkout URLs, safety assessment, and authority state (SHOULD/CAN/SHOULDNT/ESCALATE/CANT).
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | Filter to a specific brand | |
| query | Yes | Natural language query about product needs | |
| domain | No | Product domain (e.g. 'skincare', 'beauty_devices'). Auto-detected from merchant if omitted. | |
| strategy | No | Optional offer strategy override |
search_productsBrowse and search the product catalog. Use when the user wants to see what's available, look up specific products, browse by category, compare options, or asks 'show me' / 'what do you have.' Do not use when the user needs personalized recommendations based on skin concerns — use skincare_recommend instead. Returns all matching products with prices, images, and checkout. Unlike skincare_recommend, this does not score or filter — it shows everything that matches so the user can decide.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query (e.g. 'vitamin c serum', 'anti-aging', 'moisturizer under $50') | |
| category | No | Filter by exact product category from the catalog (e.g. 'serum', 'treatment', 'cleanser', 'moisturizer'). Do not guess categories — only use this if the user explicitly mentions a catalog category. For general queries like 'devices' or 'bundles', use the query parameter instead. | |
| max_price | No | Filter to products at or below this price | |
| max_results | No | Maximum products to return (default 10). Only set this if the user specifies a count — e.g. 'show me 2 devices' → 2. Otherwise leave it unset and the default will return all relevant matches up to 10. |
search_research_notesSearch SearchShopAI's Research Notes blog — data studies, playbooks, and field notes on agentic commerce (AI attribution, MCP, AI catalog accuracy, ChatGPT ads). Returns matching articles with titles, summaries, and URLs. Use when asked what SearchShopAI has written or published about a topic.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Topic or keywords, e.g. 'attribution', 'MCP', 'hallucinated prices' |
shopStart here for any shopping request. Pass the shopper's COMPLETE request in their own words and this tool will understand it and route to the right capability (personalized recommendation, catalog search, product lookup, or comparison), preserving every qualifier — concerns, skin type, budget, brand, medical context. Prefer this tool whenever the request is conversational or carries any nuance. The granular tools (search_products, get_product, compare_products, create_checkout) remain available as precise follow-ups.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | Secondary hint only — brand filter if stated. | |
| intent | No | Secondary hint only — the primary signal is `request`. | |
| request | Yes | The shopper's complete request in their own words. Include every detail: concern, skin type, budget, brand, product names, questions, medical context. Do not summarize or drop qualifiers. | |
| budget_max | No | Secondary hint only — maximum budget if stated. | |
| product_refs | No | Secondary hint only — exact product titles/SKUs when already known. |
skincare_cartInspectCreate a buyable shopping cart with a real checkout URL. Two modes: (1) Pass 'products' array with specific product names. (2) Pass 'query' string to auto-recommend and cart. Do not use for browsing or recommendations — use search_products or skincare_recommend first. Returns a widget with the cart items and a working checkout link.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Natural language query to auto-recommend products. Only used if products array is not provided. | |
| products | No | Specific product titles to add to the cart | |
| strategy | No | Optional offer strategy override when using query mode |
skincare_recommend(Deprecated: use 'recommend' instead. Works identically.) Get a personalized skincare recommendation with ingredient-aware scoring, safety notes, and routine building. Use when the user wants advice, has a skin concern, or asks what to buy. Do not use for browsing or listing products — use search_products instead. Returns scored products with checkout URLs.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | Filter to a specific brand only (e.g. 'Glossier', 'CeraVe', 'The Ordinary'). Use when the user asks for products from a specific brand. | |
| query | Yes | Natural language query about skin concerns (e.g. 'I have oily acne-prone skin and want something gentle under $30') | |
| strategy | No | Optional offer strategy override: starter, gentle, budget, glow_safe, minimal, strong, fallback |
skincare_report_issueInspectReport when a tool result was unhelpful, incomplete, or wrong. Call this whenever you override a recommendation, skip a cart result, or notice the engine output doesn't match what the user needs. Do not use proactively — only when you observe an actual issue. This helps improve the engine.
| Name | Required | Description | Default |
|---|---|---|---|
| tool_name | Yes | Which tool had the issue (skincare_recommend, skincare_cart, skincare_report_issue) | |
| issue_type | Yes | Type of issue | |
| user_query | No | The original user query if available | |
| description | Yes | What went wrong and what you expected instead | |
| expected_products | No | What products should have been recommended |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
