ShopSavvy Data API MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHOPSAVVY_API_KEY | Yes | Your ShopSavvy Data API key (starts with ss_live_ or ss_test_) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| product_lookupB | Look up a product by barcode, ASIN, URL, model number, or ShopSavvy product ID |
| product_lookup_batchA | Look up multiple products at once using comma-separated identifiers |
| product_offersA | Get current pricing offers for a product from all retailers |
| product_offers_retailerB | Get current pricing offers for a product from a specific retailer |
| product_price_historyB | Get historical pricing data for a product within a specific date range |
| product_scheduleB | Schedule products for automatic price monitoring at regular intervals |
| product_unscheduleA | Remove products from the automatic price monitoring schedule |
| scheduled_products_listA | View all products currently scheduled for automatic price monitoring |
| api_usageA | View current API usage statistics |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct operation: lookup vs batch lookup, all-retailer offers vs specific-retailer offers, schedule vs unschedule, plus a dedicated usage tool. There is no meaningful overlap or ambiguity between tool purposes.
Most tools follow a clear product_<action> pattern (product_lookup, product_offers, product_schedule, product_unschedule). One exception is scheduled_products_list, which inverts the pattern and would be more consistent as product_list_scheduled, but overall the naming is predictable.
Nine tools is well-scoped for a product data API server. Each tool covers a distinct function—lookup, offers, history, scheduling, and usage—without unnecessary redundancy or bloat.
The surface covers core product lookup, offers, price history, and scheduling lifecycle (schedule, unschedule, list). A minor gap is the lack of an update mechanism for scheduled monitoring intervals, but the primary workflows are fully supported.