How to Extract Product Specifications for Comparison with Claude

Extract product specifications with Claude and ToolRouter. Pull structured technical data from catalogues and generate comparison insights or buying guidance.

Tool
Catalogue Scraper icon
Catalogue Scraper

Use Claude with Catalogue Scraper to extract product specifications and produce comparison analysis. Claude is well-suited for this because specs across manufacturers are inconsistently named — Claude can normalize the attribute names, identify the dimensions that actually matter for comparison, and generate the comparison narrative.

Connect ToolRouter to Claude

1Open connector settings Open Settings
2Add a custom connector with these details
Name
ToolRouter
URL
https://api.toolrouter.com/mcp
3Let Claude set you up Open Claude

Steps

Once connected (see setup above), use the Catalogue Scraper tool:

  1. Provide the catalogue URL and the product category you are building comparisons for.
  2. Ask Claude to use `catalogue-scraper` with `scrape_catalogue` to extract the products and their specification fields.
  3. Ask Claude to normalize the spec field names across different manufacturers.
  4. Have Claude generate a feature matrix and a buying-guide style comparison narrative for the category.

Example Prompt

Try this with Claude using the Catalogue Scraper tool
Use catalogue-scraper to extract products from https://retailer.com/laptops. Extract every specification field available — CPU, RAM, storage, display, weight, battery. Normalize the field names across manufacturers. Then produce a feature matrix for the top 10 laptops and a short buying-guide paragraph for three price tiers (budget, mid, premium).

Tips

  • Specify the category so Claude knows which specs matter — laptop specs differ from tablet specs even though the field names overlap.
  • Ask Claude to normalize inconsistent field names (eg 'RAM' vs 'Memory' vs 'System RAM') before building the comparison.
  • Ask for a buying-guide narrative alongside the matrix — it's the deliverable that content teams actually use.