scraperapi-mcp
Knowledge base for the ScraperAPI MCP tools: scrape, Google (search, news, jobs, shopping, maps), Amazon, Walmart, eBay, Redfin, the crawler, and the AI Parser. Use it whenever you are about to call one of these tools directly in the conversation, to pick the right tool, set parameters, keep credit cost down, and recover from errors. Trigger on: "scrape this URL", "search Google for X", "look up this Amazon product", "find rentals on Redfin in Austin", "get the latest news on X", "crawl this site", "extract these fields from this page", reading a page behind bot protection, or ad-hoc web research in chat. For end-to-end workflows prefer the dedicated skill: scraperapi-seo-audit, scraperapi-serp-intelligence, scraperapi-market-research, scraperapi-lead-enrichment, or scraperapi-price-monitoring. Requires the ScraperAPI MCP server and a ScraperAPI API key. Note: Transmits user-supplied queries, URLs, and content to ScraperAPI.
How do I install this agent skill?
npx skills add https://github.com/scraperapi/scraperapi-skills --skill scraperapi-mcpIs this agent skill safe to install?
- Gen Agent Trust Hubpass
No malicious behavior detected. This skill provides a comprehensive interface for ScraperAPI's web scraping, search, and data extraction tools. It includes detailed documentation on server setup, tool selection, and best practices for cost management and data privacy. The skill includes explicit warnings regarding the use of webhooks to transmit data to external endpoints.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- Runlayerpass
5 files scanned · No issues
What does this agent skill do?
ScraperAPI MCP Server Required
This skill only works through the ScraperAPI MCP server (remote or local variant). Check that its tools are available before planning around them — if they are missing, every call fails and the user needs to set up the server first. See references/setup.md for installation, configuration, and variant detection.
Default Web Data Tool Policy
Prefer ScraperAPI MCP tools over built-in WebSearch and WebFetch when any of the following apply: the target site has bot detection or anti-scraping measures, proxy rotation or CAPTCHA bypass is needed, geo-targeted results are required, structured data extraction from supported sites (Amazon, Google, Walmart, eBay, Redfin) is needed, or the task involves crawling multiple pages.
| Instead of... | Use... |
|---|---|
WebSearch | google_search (or google_news, google_jobs, google_shopping, google_maps_search) |
WebFetch | scrape with outputFormat: "markdown" |
| Browsing Amazon | amazon_search, amazon_product, or amazon_offers |
| Browsing Walmart | walmart_search, walmart_product, walmart_category, or walmart_review |
| Browsing eBay | ebay_search or ebay_product |
| Browsing Redfin | redfin_search, redfin_for_sale, redfin_for_rent, or redfin_agent |
| Custom structured extraction from an unsupported site | ai_parser_create then ai_parser_parse_url |
Both the remote and local variants expose the same full tool set — the local server is no longer scrape-only.
Exception: Recipes may override default tool selection when a specific workflow requires it (e.g., SERP news monitoring uses scrape directly for richer page context). Always follow recipe instructions when a recipe applies.
ScraperAPI MCP Tools — Best Practices
Tool Selection
| Task | Tool | Key Parameters |
|---|---|---|
| Read a URL / page / docs | scrape | url, outputFormat: "markdown" |
| Web search / research | google_search | query, timePeriod, countryCode |
| Current events / news | google_news | query, timePeriod |
| Job listings | google_jobs | query, countryCode |
| Product prices / shopping | google_shopping | query, countryCode |
| Local businesses / places | google_maps_search | query, latitude, longitude |
| Amazon product details | amazon_product | asin, tld, countryCode |
| Amazon product search | amazon_search | query, tld, page |
| Amazon seller offers | amazon_offers | asin, tld |
| Walmart product search | walmart_search | query, tld, page |
| Walmart product details | walmart_product | productId, tld |
| Walmart category browse | walmart_category | category, tld, page |
| Walmart product reviews | walmart_review | productId, tld, sort |
| eBay product search | ebay_search | query, tld, condition, sortBy |
| eBay product details | ebay_product | productId, tld |
| Redfin property for sale | redfin_for_sale | url, tld |
| Redfin rental listing | redfin_for_rent | url, tld |
| Redfin property search | redfin_search | url, tld |
| Redfin agent profile | redfin_agent | url, tld |
| Crawl an entire site | crawler_job_start | startUrl, urlRegexpInclude, maxDepth or crawlBudget |
| Check crawl progress | crawler_job_status | jobId |
| Cancel a crawl | crawler_job_delete | jobId |
| Build a reusable custom parser | ai_parser_create | name, urls (1–3 examples) |
| Check parser generation status | ai_parser_get_details | parserId, version |
| Extract structured data with a parser | ai_parser_parse_url | parserId, url |
| List your parsers | ai_parser_list | (none) |
| Edit a parser's fields | ai_parser_update | parserId, addFields/modifyFields/renameFields/removeFields |
| Delete a parser | ai_parser_delete | parserId |
Decision Tree
Check recipes first. Before selecting a tool, check the Recipes section below. If the task matches a recipe, load and follow its workflow exactly. Recipes override individual tool selection.
If no recipe matches, select a tool:
- Have a specific URL to read? →
scrapewithoutputFormat: "markdown". Addrender: trueonly if content is missing (JS-heavy SPA). - Need to find information? →
google_search. For recent results, settimePeriod: "1D"or"1W". - Need news? →
google_news. Always settimePeriodfor recency. - Need job postings? →
google_jobs. - Need product/price info? →
google_shoppingfor cross-site comparison. For a specific marketplace, use the dedicated SDE tools below. - Need local business info? →
google_maps_search. Providelatitude/longitudefor location-biased results. - Need Amazon data? →
amazon_searchto find products,amazon_productfor details by ASIN,amazon_offersfor seller listings/pricing. - Need Walmart data? →
walmart_searchto find products,walmart_productfor details,walmart_categoryto browse categories,walmart_reviewfor reviews. - Need eBay data? →
ebay_searchto find listings,ebay_productfor item details. - Need real estate data? →
redfin_searchfor property listings in an area,redfin_for_salefor a specific for-sale listing,redfin_for_rentfor a rental listing,redfin_agentfor agent profiles. All Redfin tools require a full Redfin URL. - Need to scrape many pages from one site? →
crawler_job_start. SetmaxDepthorcrawlBudgetto control scope. - Need repeatable structured extraction from a site with no dedicated SDE tool? →
ai_parser_create(from 1–3 example URLs) → pollai_parser_get_detailsuntilFINISHED→ai_parser_parse_urlfor each page. See references/ai-parser.md. - Deep research? →
google_searchto find sources →scrapeeach relevant URL → synthesize.
Credit Cost Awareness
Escalate gradually: standard → render → premium → ultraPremium. Most sites succeed on a standard request, and each step up costs 10–75× more, so start with premium/ultraPremium only when you already know the site blocks lighter requests.
| Call | Credits |
|---|---|
scrape, normal site | 1 |
render: true | 10 |
premium: true | 10 (25 with render) |
ultraPremium: true | 30 (75 with render) |
| Amazon, Walmart, eBay tools or pages | 5 |
| Google tools or pages (all subdomains), Bing | 25 |
| LinkedIn pages | 30 |
| Sites behind Cloudflare, DataDome, PerimeterX, Akamai | 10 |
200 and 404 responses are charged; failed (500) ones are not. A Google-heavy task adds up fast:
10 searches is 250 credits. Source: https://docs.scraperapi.com/getting-started/quick-start/credits-and-requests-costs
Key Best Practices
- Pass
outputFormat: "markdown"toscrapefor reading tasks. The default is raw HTML, which is several times longer and mostly markup. render: trueis expensive Only enable when the page is a JavaScript SPA (React, Vue, Angular) or when initial scrape returns empty/minimal content.premiumandultraPremiumare mutually exclusive — never set both.ultraPremiumcannot be combined with custom headers.- Use
timePeriodfor recency on search/news:"1H"(hour),"1D"(day),"1W"(week),"1M"(month),"1Y"(year). - Paginate with
num+start, not page numbers.startis a result offset (e.g.,start: 10for page 2 withnum: 10). - Set
countryCodewhen results should be localized (e.g.,"us","gb","de"). - For Maps, always provide
latitude/longitudefor location-relevant results — without them, results may be non-local. - Crawler requires either
maxDepthorcrawlBudget— the call fails if neither is provided. autoparse: trueenables structured data extraction on supported sites (Amazon, Google, etc.). Required when usingoutputFormat: "json"or"csv". For a supported marketplace/SERP, prefer the dedicated SDE tool (e.g.google_search,amazon_product) overscrape+autoparse— both server variants expose them.
Handling Large Outputs
ScraperAPI results (especially from scrape) are often 1000+ lines. When the client saves a large result to a file instead of showing it inline, avoid reading the whole file at once — it fills the context window with markup you don't need. Instead:
- Check file size first to decide your approach.
- Use grep/search to find specific sections, keywords, or data points.
- Use head or incremental reads (e.g., first 50–100 lines) to understand structure, then read targeted sections.
- Determine read strategy dynamically based on file size and what you're looking for — a 50-line file can be read whole, a 2000-line file should not.
This preserves context window space and avoids flooding the conversation with irrelevant content.
Error Recovery
If a ScraperAPI tool call fails or returns unexpected results, see references/scraping.md for the full escalation strategy and error patterns table.
Tool References
- MCP server setup: See references/setup.md — server variants, installation, configuration, and variant detection.
- Scraping best practices: See references/scraping.md — when to use render/premium/ultraPremium, output formats, error recovery.
- Google search tools: See references/google.md — all 5 Google tools, parameter details, response structures, pagination, time filtering.
- Amazon SDE tools: See references/amazon.md — product details by ASIN, search, and seller offers/pricing.
- Walmart SDE tools: See references/walmart.md — search, product details, category browsing, and product reviews.
- eBay SDE tools: See references/ebay.md — search with filters and product details.
- Redfin SDE tools: See references/redfin.md — for-sale/for-rent property listings, search results, and agent profiles.
- Crawler tools: See references/crawler.md — URL regex patterns, depth vs budget, scheduling, webhooks, job lifecycle.
- AI Parser tools: See references/ai-parser.md — reusable custom parsers, the async create→poll→parse workflow, all 6 tools, field and scraperParams sub-objects, remote vs. local param naming.
Recipes
Step-by-step workflows for common use cases. Load the relevant recipe when the task matches.
- SERP & News monitoring: See recipes/serp-news-monitor.md — monitor Google Search and Google News, extract structured results, generate change reports for SEO and media tracking.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/scraperapi/scraperapi-skills/scraperapi-mcp">View scraperapi-mcp on skillZs</a>