Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
linkfox-ai avatar

Linkfox Amazon Search

  • 281 installs
  • 64 repo stars
  • Updated August 3, 2026
  • linkfox-ai/linkfox-skills

Search Amazon listings with LinkFox to map competitor ASINs, titles, reviews, and positioning while exploring new product ideas.

About

linkfox-amazon-search skill enables agent-assisted Amazon product and keyword search through LinkFox. Teams use it in early discovery to study competitor listings, pricing cues, and review patterns that shape initial product and positioning hypotheses.

  • ASIN and keyword search
  • Competitor listing scans
  • Review and rank signals
  • Merchandising comparisons
  • Agent-queryable catalog data

Linkfox Amazon Search by the numbers

  • 281 all-time installs (skills.sh)
  • +39 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #250 of 853 Sales & Marketing skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/linkfox-ai/linkfox-skills --skill linkfox-amazon-search

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs281
repo stars64
Last updatedAugust 3, 2026
Repositorylinkfox-ai/linkfox-skills

What it does

Search Amazon listings with LinkFox to map competitor ASINs, titles, reviews, and positioning while exploring new product ideas.

Files

SKILL.mdMarkdownGitHub ↗

Amazon Product Search

This skill guides you on how to perform Amazon storefront search simulations, helping Amazon sellers retrieve real-time search result data including product rankings, prices, ratings, and more.

Core Concepts

This tool simulates a real user searching on Amazon's storefront. It returns live search result page (SERP) data: product listings with their positions, prices, ratings, review counts, brands, delivery info, sponsored flags, and more. This is real-time data directly from the Amazon frontend, not historical analytics.

Key distinction from ABA data: ABA data is aggregated historical search term analytics. This tool returns the actual product listings a user would see when searching a keyword on Amazon right now.

Keyword language: Keywords should be in the language of the target marketplace. For example, use English keywords for amazon.com, German keywords for amazon.de, Japanese keywords for amazon.co.jp, etc.

Parameters

ParameterTypeRequiredDescriptionDefault
keywordstringNoSearch keyword (translate to the target marketplace's language)-
amazonDomainstringNoAmazon marketplace domainamazon.com
nodestringNoAmazon category node ID for category-scoped searches-
languagestringNoLanguage locale code (e.g., en_US, de_DE, ja_JP)-
sortstringNoSort order for resultsrelevanceblender
pageintegerNoPage number (starting from 1, ~20 results per page)1
deliveryZipstringNoPostal/zip code for delivery location simulation-
devicestringNoDevice type: desktop, mobile, or tabletdesktop

Supported Marketplaces

DomainCountry
amazon.comUnited States
amazon.co.ukUnited Kingdom
amazon.deGermany
amazon.frFrance
amazon.itItaly
amazon.esSpain
amazon.co.jpJapan
amazon.caCanada
amazon.com.auAustralia
amazon.com.brBrazil
amazon.inIndia
amazon.nlNetherlands
amazon.seSweden
amazon.plPoland
amazon.sgSingapore
amazon.saSaudi Arabia
amazon.aeUnited Arab Emirates
amazon.com.mxMexico
amazon.com.trTurkey
amazon.com.beBelgium
amazon.cnChina
amazon.egEgypt

Default marketplace is amazon.com. Use amazon.com when the user doesn't specify a marketplace.

Sort Options

ValueDescription
relevanceblenderFeatured / Relevance (default)
price-asc-rankPrice: Low to High
price-desc-rankPrice: High to Low
review-rankAverage Customer Review
date-desc-rankNewest Arrivals
exact-aware-popularity-rankBest Sellers

API Usage

This tool calls the LinkFox tool gateway API. See references/api.md for calling conventions, request parameters, and response structure. You can also execute scripts/amazon_search.py directly to run queries.

How to Build Queries

Construct the request parameters based on the user's intent:

1. Determine the marketplace: Map the user's target country to the correct amazonDomain value 2. Set the keyword: Translate the search term into the target marketplace's language 3. Choose sort order: If the user wants results sorted by price, reviews, or newness, set the sort parameter 4. Pagination: Use the page parameter to fetch additional result pages if needed 5. Category scope: If the user wants to search within a specific category, provide the node parameter 6. Delivery simulation: Use deliveryZip to see location-specific availability and delivery info

Usage Examples

1. Basic keyword search on US marketplace

{"keyword": "wireless earbuds", "amazonDomain": "amazon.com"}

2. Search on German marketplace with German keyword

{"keyword": "kabellose Kopfhoerer", "amazonDomain": "amazon.de", "language": "de_DE"}

3. Search sorted by price (low to high)

{"keyword": "phone case", "amazonDomain": "amazon.com", "sort": "price-asc-rank"}

4. Search for best sellers in a category

{"keyword": "yoga mat", "amazonDomain": "amazon.com", "sort": "exact-aware-popularity-rank"}

5. Search for newest arrivals on Japan marketplace

{"keyword": "USB充電器", "amazonDomain": "amazon.co.jp", "language": "ja_JP", "sort": "date-desc-rank"}

6. Multi-page search to analyze deeper results

{"keyword": "laptop stand", "amazonDomain": "amazon.com", "page": 2}

7. Mobile device search simulation

{"keyword": "running shoes", "amazonDomain": "amazon.com", "device": "mobile"}

8. Category-scoped search with delivery zip

{"keyword": "office chair", "amazonDomain": "amazon.com", "deliveryZip": "10001"}

Display Rules

1. Present data clearly: Show search results in well-structured tables with key fields: position, ASIN, title, price, rating, review count, brand 2. Highlight sponsored products: Clearly mark which results are sponsored ads vs organic listings 3. Price formatting: Display prices with the correct currency symbol for the marketplace 4. Position context: Remind users that position reflects the actual ranking on the search result page 5. Pagination notice: When results span multiple pages, inform the user how many total results were found and suggest fetching additional pages if needed 6. Error handling: When a query fails, explain the reason based on the error response and suggest adjusting parameters 7. Image links: If image URLs are available, mention them but do not attempt to render them inline unless the user requests it

Important Limitations

  • Real-time only: This tool returns live search results, not historical data. For historical search term analytics, use ABA data instead
  • Rate awareness: Each call simulates a real search request; avoid excessive rapid-fire calls
  • ~20 results per page: Each page returns approximately 20 product listings
  • Keyword language matters: Results quality depends on using the correct language for the target marketplace

User Expression & Scenario Quick Reference

Applicable -- Real-time Amazon search result queries:

User SaysScenario
"Search for XX on Amazon"Basic product search
"What products appear for keyword XX"Keyword SERP analysis
"Where does my ASIN rank for XX keyword"Position / ranking check
"Show me the top results for XX"Competitive landscape
"What's the price range for XX"Price comparison
"Any sponsored products for XX keyword"Sponsored ad analysis
"New products for XX keyword"New arrival monitoring
"Search XX on Amazon Germany/Japan/UK"Cross-marketplace search
"What are the best sellers for XX"Best seller discovery
"Compare search results on mobile vs desktop"Device-specific SERP

Not applicable -- Needs beyond real-time search results:

  • Historical search term volume or ranking trends (use ABA data)
  • Advertising campaign management or bid optimization
  • Product review analysis or sentiment analysis
  • Sales estimation or revenue analytics
  • Listing optimization or copywriting suggestions
  • Inventory or supply chain data

Boundary judgment: When users say "product research" or "competitor analysis", if it boils down to seeing what currently appears on Amazon search results for a keyword (product positions, prices, ratings), then this skill applies. If they want historical trends, search volume data, or aggregated analytics, ABA data is more appropriate.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply: 1. The functionality or purpose described in this skill does not match actual behavior 2. The skill's results do not match the user's intent 3. The user expresses dissatisfaction or praise about this skill 4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

<!-- LF_LARGE_RESPONSE_BLOCK -->

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/amazon_search.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"
Pick --out-dir outside any git working tree (e.g. /tmp/... on Unix, %TEMP%/... on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

run writes the full response to a file and emits only a schema preview + file path. read projects specific fields, with --limit/--offset for slicing and --format json|jsonl|csv|table for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

  • High field count per record, or fields you don't need
  • Batch/paginated results (multiple items per call)
  • Long-text fields (descriptions, reviews, HTML, time series)
  • Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via read. <!-- /LF_LARGE_RESPONSE_BLOCK -->

--- For more high-quality, professional cross-border e-commerce skills, set [LinkFox Skills](https://skill.linkfox.com/).

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.