Use when you need to research a product online to find its retail price, used market value, official description, specifications, and measurements. Invoke after identifying brand/model from images.
Every accurate FB Marketplace listing in our workflow starts here. We never guess prices or descriptions - we research them.
Before proceeding, you MUST:
digraph research_flow {
rankdir=TB;
node [shape=box];
start [label="Start with product identifier" shape=ellipse];
search [label="1. Web search for exact product"];
find_retail [label="2. Find retail listings\n(Amazon, manufacturer, retailers)"];
find_used [label="3. Search used marketplaces\n(eBay sold, FB Marketplace, Craigslist)"];
extract_desc [label="4. Extract official description"];
extract_specs [label="5. Extract specifications/measurements"];
estimate_price [label="6. Calculate price range"];
output [label="Return research summary" shape=ellipse];
start -> search;
search -> find_retail;
find_retail -> find_used;
find_used -> extract_desc;
extract_desc -> extract_specs;
extract_specs -> estimate_price;
estimate_price -> output;
}
Prefer WebSearch over WebFetch. WebSearch returns rich summaries directly and is fast/reliable. WebFetch often hangs or fails on retailer sites (Costco, Amazon, etc.).
Run searches in parallel when they don't depend on each other.
IMMEDIATELY run these WebSearch queries in parallel:
"[Brand] [Model]" specifications price (primary search)[Brand] [Model] site:ebay.com sold (used market pricing)[Brand] [Model] review (features and real-world info)WebSearch results typically include prices directly. Look for:
Record:
From WebSearch results, extract:
Never write our own marketing copy when official descriptions exist.
Always look for these - missing specs make listings fail:
We always use this pricing table - no exceptions:
| Condition | Suggested Price |
|---|---|
| Like New / Sealed | 60-75% of retail |
| Excellent (minimal use) | 50-60% of retail |
| Good (normal wear) | 40-50% of retail |
| Fair (visible wear) | 25-40% of retail |
You MUST adjust based on:
Every research summary MUST follow this exact format:
## Research Summary: [Product Name]
### Product Identification
- **Brand**: [Brand]
- **Model**: [Model Number]
- **Full Name**: [Official Product Name]
### Pricing
- **Retail Price**: $XX (source)
- **Used Market Range**: $XX - $XX
- **Recommended Listing Price**: $XX - $XX
### Description
[Official product description or synthesized description from research]
### Specifications
- Dimensions: [H x W x D]
- Weight: [Weight]
- [Other relevant specs]
### Key Features
- [Feature 1]
- [Feature 2]
- [Feature 3]
### Sources
- [URL 1]
- [URL 2]
| Mistake | Result | Fix |
|---|---|---|
| Using WebFetch on retailer sites | Hangs or fails, wastes time | Use WebSearch - it returns prices in snippets |
| Using retail price as listing price | Item never sells, wastes seller's time | Always discount 25%-30% for used items |
| Missing model number in search | Wrong product, wrong price, angry buyer | Always include exact model for accurate results |
| Ignoring condition in pricing | Overpriced items sit unsold for weeks | Always adjust price based on actual item condition |
| Single source for pricing | Wildly inaccurate estimates | Always check multiple sources - minimum of 3 |
| Skipping specifications | Buyers ask questions, listing looks amateur | Always extract dimensions and key specs |
| Writing custom descriptions | Inconsistent quality, missing features | Always use official descriptions when available |
| Running searches sequentially | Slow research, user waiting | Run independent WebSearch queries in parallel |