ASIN Data API
ASIN Data API provides detailed product data from Amazon, including price, rank, reviews, and more, enabling real-time insights for e-commerce professionals, marketers, and data analysts.
Verdict
Common use cases
- Review product collections during planning meetings
- Clean up old ASIN tracking requests
- Audit competitor product catalogs in real time
- Paginate through large product datasets quickly
Integration
- Vendor
- ASIN Data API
- Category
- other
- Auth
- API_KEY
- Tools
- 2
- Composio slug
asin_data_api
Tools
- Clear multiple collection requests
Tool to delete multiple requests from a collection by ids. use when you need to remove a selected set of request entries from an existing collection in a single call.
- List Collection Requests
Tool to list all requests in a collection (paginated). use when you need to paginate through requests for a specific collection.
Setup
Setup guide
- 11. Go to the ASIN Data API website and sign up for an account to generate your API key. 2. In Switchy, open Settings and navigate to the Integrations or MCP Connections section. 3. Click Add Integration and select ASIN Data API from the list. 4. Paste your API key into the authentication field and click Connect. 5. Switchy will validate the key and confirm the connection is active. 6. Open any Space and type '@ASIN Data API list requests in collection [collection_id]' to test the integration. 7. If the MCP returns paginated request data, the connection is working and you can start managing your product collections from chat.
What teammates see: by default, memories from ASIN Data API are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Collection Requests
@ASIN Data API list all requests in collection abc123, starting from page 1. Show me the first 20 entries so I can review what we're monitoring.Open in a Space →
Clear Stale Requests
@ASIN Data API delete requests with IDs req_001, req_002, req_003 from collection abc123. These are old products we no longer need to track.Open in a Space →
Audit Collection Size
@ASIN Data API show me the total count of requests in collection abc123, then list the first page so I can see what's in there.Open in a Space →
Batch Clean Collections
@ASIN Data API remove these request IDs from collection xyz789: req_101, req_102, req_103, req_104, req_105. We finished analyzing them last week.Open in a Space →
Review Recent Additions
@ASIN Data API list requests in collection abc123, sorted by most recent. Show me the last 10 entries added this week.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@ASIN Data API show me all the product lookup requests in collection 'q4-electronics' from the last week
Retrieved 47 requests from collection 'q4-electronics'. Recent entries include: ASIN B08N5WRWNW (requested 2024-12-18, status: completed), ASIN B09G9FPHY6 (requested 2024-12-17, status: completed), ASIN B0BDJ7KQXV (requested 2024-12-16, status: pending). The collection spans 3 pages; currently showing page 1 of 3. Each request includes timestamp, ASIN identifier, completion status, and associated metadata fields.
This example demonstrates the List Collection Requests tool with pagination. Users should know that collections must be created beforehand via the ASIN Data API dashboard or separate endpoints. The MCP returns metadata about requests, not the actual product data itself—you'll need to correlate request IDs with your data pipeline to retrieve results.
@ASIN Data API remove requests with IDs req_8x3k, req_9m2p, and req_4n7q from the 'test-batch' collection
Successfully deleted 3 requests from collection 'test-batch'. Removed entries: req_8x3k (ASIN B07XJ8C8F5, created 2024-12-10), req_9m2p (ASIN B08L5VG9K3, created 2024-12-11), req_4n7q (ASIN B09JQFH8WZ, created 2024-12-12). The collection now contains 14 remaining requests. Note that deletion is permanent and does not affect any product data already retrieved from these requests.
This example shows the Clear Multiple Collection Requests tool for batch cleanup. Users must provide exact request IDs—the MCP cannot search by ASIN or date range for deletion. This is a destructive operation with no undo, so confirm IDs carefully before running. Useful for managing collection size and removing test entries.
@ASIN Data API list all requests in 'competitor-tracking' and summarize which ASINs have pending status versus completed
Collection 'competitor-tracking' contains 82 total requests across 4 pages. Status breakdown: 68 completed (82.9%), 12 pending (14.6%), 2 failed (2.4%). Pending ASINs include B0CXJ9K2L7, B0D1M8N4P3, B0CWQR5T6V (all submitted within the last 6 hours). Failed requests are B08ZYX1W2V and B09ABC3D4E, both returning 'ASIN not found' errors. The completed requests span a date range from 2024-11-15 to present, suggesting this is an active monitoring collection.
This example pairs the List Collection Requests tool with AI reasoning to synthesize status patterns. The MCP provides raw request metadata; the AI interprets counts and trends. Users should be aware that 'pending' status may indicate API rate limits or queue delays on the ASIN Data API side, not an error with the MCP itself.
Use-case deep-dives
When batch-deleting stale ASIN requests makes sense
A 6-person e-commerce ops team runs daily ASIN lookups to sync product data from Amazon into their Shopify catalog. Over weeks, their collection fills with thousands of completed or failed requests that clutter the queue. The clear-multiple-requests tool lets them purge 50-100 stale entries at once during Monday morning cleanup, instead of manually clicking through a UI. This MCP works if your team already uses ASIN Data API's collection feature and you're hitting pagination limits when browsing requests. If you're only running a handful of lookups per week, the overhead of setting up this MCP outweighs the time saved. Best fit: teams doing 200+ ASIN requests monthly who need programmatic housekeeping.
Paginating through ASIN request history for reporting
A 3-person growth team at a DTC brand tracks competitor pricing by queuing ASIN lookups for 80 rival products every Friday. They need to audit which requests succeeded, which failed, and which ASINs returned null prices. The list-collection-requests tool pages through the week's batch so they can export results to a spreadsheet without opening the ASIN Data API dashboard. This scenario assumes your team already stores requests in a named collection and you're comfortable writing a script to loop through pages. If you're only checking 10-15 ASINs sporadically, manually copying results from the web UI is faster. Use this MCP when your audit cadence is weekly or more frequent and you're reviewing 50+ requests per session.
When two tools aren't enough for product research workflows
A 2-person dropshipping side-hustle uses ASIN Data API to validate product availability before listing items. They hoped this MCP would let them query ASIN details, check stock levels, and compare prices across regions. It doesn't. The two available tools only manage the request collection itself—deleting old entries and listing them—not fetching or analyzing ASIN data. For actual product research, you'd need the vendor's other endpoints exposed through a different integration or direct API calls. This MCP is a narrow utility for teams already deep in ASIN Data API's workflow who need to script collection maintenance. If you're evaluating ASIN Data API for the first time, start with their web dashboard or full API before adding this MCP.
Frequently asked
What does the ASIN Data API MCP do in Switchy?
It lets your team retrieve and manage Amazon product data (ASINs) through Switchy's AI workspace. You can query product details, manage collections of requests, and delete batches of entries without switching to a separate dashboard. Useful for e-commerce teams tracking competitor pricing, inventory research, or building product catalogs from Amazon data.
Do I need special permissions to connect ASIN Data API?
You need an API key from ASIN Data API — no OAuth flow or admin approval required. Whoever holds the key can connect it to Switchy. If your team shares one account, consider creating a dedicated API key for Switchy so you can rotate or revoke it independently of other integrations.
Can this MCP pull real-time Amazon product prices?
The MCP exposes collection management tools (listing and deleting requests), not direct product lookups. If ASIN Data API's underlying service supports price queries, you'll interact with those via the collection workflow. Check the vendor's API docs to confirm which ASIN fields (price, reviews, availability) your plan includes before connecting.
How is this different from scraping Amazon directly?
ASIN Data API handles rate limits, proxy rotation, and parsing for you — scraping Amazon yourself risks IP bans and constant HTML changes. The MCP brings that vendor service into Switchy so your team can query product data in natural language instead of writing scraper scripts or API calls.
Who on the team should connect this MCP?
Whoever manages your ASIN Data API subscription and holds the API key. Once connected in Switchy, any workspace member can use it (subject to your Switchy plan). The API key itself doesn't expire unless you regenerate it on the vendor side, so one connection covers the whole team.