mcpField
F
firecrawl-build-scrape

firecrawl-build-scrape

github.com/firecrawlData & databases13961.8k installsUpdated 6d ago
Repository

About firecrawl-build-scrape

A Firecrawl integration skill for applications that already have a URL and need content from one page. It guides extraction choices, freshness checks, and when to switch to search or browser interaction.

Key features

  1. 01Extract content from a known URL
  2. 02Choose Markdown and main-content options
  3. 03Set cache age for freshness needs
  4. 04Inspect cache metadata
  5. 05Escalate search or multi-step browsing

Use cases

  1. 01Ingest knowledge from known pages
  2. 02Extract documentation or changelog content
  3. 03Enrich records with company or product pages
  4. 04Check page content for quality or changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/firecrawl/skills --skill firecrawl-build-scrape

After installing, type/firecrawl-build-scrapein Claude Code to confirm it loaded.

Bundled filesreferences/freshness-and-liveness.md

Details

From the project README

Firecrawl Build Scrape

Use this when the application already has the URL and needs content from one page.

Use This When

  • the feature starts from a known URL
  • you need page content for retrieval, summarization, enrichment, or monitoring
  • you want the default extraction primitive before considering /interact

Default Recommendations

  • Return markdown unless the feature truly needs another format.
  • Use onlyMainContent for article-like pages where nav and chrome add noise.
  • Add waits or other rendering options only when the page needs them.

Freshness and Liveness

  • Firecrawl reuses recently indexed content, which is what makes repeat reads of the same URL fast. Set maxAge (milliseconds) to bound how old a reused copy may be, or maxAge: 0 to skip index reuse for a freshness-critical read.
  • Read metadata.cacheState and metadata.cachedAt to see what you actually got.
  • A successful scrape reports what the page returned. Whether the thing the page describes is still active is a source-specific judgment your code makes.
  • See references/freshness-and-liveness.md for the tradeoff, the metadata, and the decision rule.

Common Product Patterns

  • knowledge ingestion from known URLs
  • enrichment from a company, product, or docs page
  • pricing, changelog, and documentation extraction
  • page-level quality checks or monitoring

Escalation Rules

Implementation Notes

  • Keep the integration narrow: one feature, one URL, one extraction contract.
  • Treat /scrape as the default primitive for downstream LLM or indexing pipelines.
  • Request richer formats only when the consumer needs them, such as links, screenshots, or branding data.

Docs (Source of Truth)

Read the source-of-truth page for your project language before writing integration code:

See Also

Comments

Markdown supported