Brand Search Catalog Report
Review catalog and search performance for ASINs from Claude with Launch Fast MCP.
Review catalog and search performance for ASINs from Claude with Launch Fast MCP.
Brand Search Catalog Performance shows how catalog products perform in Amazon search. It gives visibility, traffic, and conversion patterns for each ASIN. Use it to find performance changes and compare marketplaces. It also identifies ASINs to examine for listing, price, inventory, or ad problems.
Brand Query Report looks at query-level funnel behavior for one ASIN. Brand Search Terms Report looks at marketplace-level search terms and clicked ASINs. Brand Search Catalog Report looks across ASINs in the catalog.
What This Report Shows
Brand Search Catalog Performance is an Amazon Brand Analytics style report focused on product-level search performance.
| Question | What the report can show |
|---|---|
| Which ASINs get search visibility? | Product-level visibility and search performance across the catalog. |
| Which catalog items gain or lose search performance? | ASINs that improve or decline with time. |
| Which ASINs have weak conversion relative to visibility? | Products with visibility but poor conversion behavior. |
| Which products must I optimize? | ASINs for which you must review content, price, reviews, images, or offers. |
| Which marketplaces perform better or worse? | Marketplace differences for the same ASIN when available. |
| Which ASINs deserve more attention? | Portfolio winners, underperformers, and outliers. |
This report helps move from search-term analysis to product-level catalog decisions.
How To Use This Report
Use this report to find product-level search performance problems.
| Pattern | Common interpretation |
|---|---|
| Good visibility and good conversion | The ASIN can be worth defending with inventory, SEO, and ads. |
| Good visibility but weak conversion | Review the listing, price, reviews, offer, images, and inventory. |
| Low visibility but good conversion | The ASIN can want more traffic through SEO or ads. |
| Marketplace differences | Review the local price, content, images, and availability for the product. |
| Portfolio outliers | Examine products that perform much worse than the other catalog products. |
Tool Details
| Field | Value |
|---|---|
| MCP tool | amazon_brand_search_catalog_performance_lookup |
| App UI | ui://launchfast/brand-search-catalog-performance |
| Behavior | Read-only |
| Amazon account required | Yes — Seller Central/SP-API connection with Brand Analytics data |
| Best for | Catalog search performance, ASIN portfolio review, low-conversion detection, marketplace comparison |
When To Use It
| Use case | What it helps you answer |
|---|---|
| Catalog search review | How ASINs perform in Amazon search across the catalog. |
| ASIN inspection | How one ASIN performs across periods and marketplaces. |
| Low-conversion detection | Which ASINs have weak search conversion. |
| Marketplace comparison | Where catalog performance differs by marketplace. |
| Listing optimization | Which product listings or offers you must review. |
| Portfolio review | Which ASINs are winners or underperformers. |
| Cross-report follow-up | Which products deserve deeper Brand Query, Brand Search Terms, Sales, Inventory, Finance, or Ads review. |
What It Returns
| Result area | What Claude can summarize |
|---|---|
| Portfolio summary | Portfolio-level catalog summary. |
| ASIN rows | ASIN-level search performance rows. |
| Low-conversion candidates | ASINs with weak conversion or poor search efficiency. |
| Marketplace comparisons | Marketplace-level differences when available. |
| Catalog visibility | Product/catalog visibility context. |
| Report context | Reporting period and date range context. |
| Account coverage | Account or connection coverage details when multiple accounts exist. |
The accurate fields depend on Brand Analytics availability and synced Launch Fast data.
Actions
| Action | Use when | Required inputs | Optional inputs |
|---|---|---|---|
summary | You want a broad summary of catalog search performance. | None | asin, seller_id, connection_id, marketplace_id, report_period, date_from, date_to, limit |
by_asin | You want to inspect one ASIN across periods and marketplaces. | asin | seller_id, connection_id, marketplace_id, report_period, date_from, date_to, limit |
low_conversion | You want ASINs with weak conversion or poor search efficiency. | None | asin, seller_id, connection_id, marketplace_id, report_period, date_from, date_to, limit |
marketplace_compare | You want to compare catalog performance across marketplaces. | None | asin, seller_id, connection_id, marketplace_id, report_period, date_from, date_to, limit |
portfolio_overview | You want a portfolio-level ASIN ranking by search traffic or sales behavior. | None | asin, seller_id, connection_id, marketplace_id, report_period, date_from, date_to, limit |
Inputs
| Input | Required | Notes |
|---|---|---|
asin | Required for by_asin. Optional elsewhere | ASIN to inspect or narrow results to. |
seller_id | No | Optional Amazon seller account filter. |
connection_id | No | Optional Launch Fast Amazon connection filter. |
marketplace_id | No | Optional Amazon marketplace filter. |
report_period | No | Reporting period filter. Supports WEEK or QUARTER. |
date_from | No | Inclusive start date in YYYY-MM-DD format. |
date_to | No | Inclusive end date in YYYY-MM-DD format. |
limit | No | Maximum rows to include. Supports 1-100. |
Example Prompts
Low-conversion review:
Find low-conversion ASINs in Brand Search Catalog Performance.Portfolio overview:
Show a portfolio overview of my catalog search performance for the last quarter.ASIN detail:
Inspect Brand Search Catalog Performance for ASIN B07HQM6NH8.Marketplace comparison:
Compare catalog search performance by marketplace for my top ASINs.Listing optimization:
Find ASINs with good visibility but weak conversion. Suggest what I must review first.Catalog winners:
Which ASINs have the strongest search performance in my catalog?Cross-report follow-up:
Compare low-conversion ASINs with Brand Query Performance funnel gaps and Amazon Ads spend.How To Read The Results
Read this report as product-level search performance.
| Signal type | Look for |
|---|---|
| Positive signals | Look for strong search visibility and conversion. Find products with consistent results across report periods. Find products that convert well with low visibility. Look for stable or better marketplace performance. |
| Risk or opportunity signals | Look for visibility with weak conversion. Find ASINs that lose search performance. Compare products that perform differently across marketplaces. Find visible products with inventory, price, review, or content problems. |
Common Analysis Patterns
Use Claude to convert catalog rows into decisions.
| Pattern | Ask Claude to identify |
|---|---|
| Low-conversion detection | Which ASINs get visibility but fail to convert. |
| Portfolio review | Which products carry catalog search performance. |
| Marketplace comparison | Where an ASIN performs worse and why that might be. |
| Listing optimization | Which ASIN images, titles, reviews, prices, or offers you must examine. |
| Ads follow-up | If low-conversion ASINs are also spending in Sponsored Products. |
| Inventory follow-up | If strong catalog performers are at risk of running out. |
| Query follow-up | Which search queries explain an ASIN's weak conversion. |
Suggested Workflow
Start With Portfolio Context
Run portfolio_overview or summary to understand catalog-wide performance.
Find Weak Conversion
Use low_conversion to find ASINs with weak search conversion.
Inspect One ASIN
Use by_asin to inspect a specific product.
Compare Marketplaces
Use marketplace_compare when performance varies by marketplace.
Review Query Funnel
Follow up with Brand Query Report to understand which queries cause funnel leaks.
Review Marketplace Terms
Follow up with Brand Search Terms Report to understand marketplace search behavior.
Connect To Account Outcomes
Follow up with Sales, Inventory, Finance, or Ads tools to connect catalog performance to account outcomes.
Common Empty Result Causes
Empty or thin results can mean no matching synced rows were found.
| Cause | Recovery |
|---|---|
| Seller Central/SP-API is not connected. | Connect Seller Central/SP-API in Settings -> Authentication. |
| Brand Analytics data has not synced yet. | Wait for Brand Analytics sync to finish. |
| Selected ASIN has no catalog performance rows. | Try portfolio-level actions first, then narrow to ASINs from the results. |
report_period has no matching data. | Try WEEK or QUARTER, depending on available data. |
| Date range is outside available synced data. | Try a broader or more recent date range. |
marketplace_id is too narrow. | Remove the marketplace filter. |
| Connected account lacks report access. | Confirm the account has access to Brand Analytics data. |
Try this recovery prompt:
Try Brand Search Catalog Performance again with a broader date range and remove ASIN, marketplace, seller, and connection filters.For one product:
Try by_asin for B07HQM6NH8 over the last quarter and include marketplace comparison if available.Safety Notes
Brand Search Catalog Performance is read-only.
| It can inspect | It does not change |
|---|---|
| Synced Brand Analytics catalog/search performance for ASINs, marketplaces, reporting periods, and portfolio views. | Listings, prices, Brand Analytics, inventory, ads, keywords, or Seller Central settings. |
Claude can recommend product, listing, inventory, SEO, or PPC follow-up actions. All account changes must be made manually outside this MCP tool.
Limits And Notes
| Area | Note |
|---|---|
| Connection | Requires a connected Amazon Seller Central/SP-API account with related Brand Analytics data. |
| Rate limit | Amazon SP-API reporting tools allow 120 reads/min for each user. |
| Data availability | Results depend on Brand Analytics data synced into Launch Fast. |
| Amazon availability | Brand Analytics availability can vary by account, ASIN, marketplace, and period. |
| Report period | report_period supports WEEK and QUARTER. |
| Date format | Dates must use YYYY-MM-DD. |
| Result size | Use limit to keep large catalog result sets concise. |