Skip to main content
Glama

Firecrawl scrape

firecrawl_scrape

Fetches a single URL and returns its content as markdown, HTML, links, screenshots, or schema-matched JSON, enabling page text extraction or defined field capture.

Instructions

Scrape one URL and return its content: markdown by default, or HTML, links, screenshots, branding data, a targeted answer, or JSON matching a supplied schema. Use it when the request identifies a page and needs its content or defined fields. Use firecrawl_search when additional web sources are needed; on an authenticated session, firecrawl_map lists a site's URLs and firecrawl_crawl collects a set of pages.

Firecrawl may serve recently indexed content; set maxAge: 0 for a live fetch or a smaller maxAge to bound staleness. A successful response does not by itself confirm the page is still current. Browser actions can change the live page when interactive actions are enabled. Authenticated responses can include a metadata.scrapeId for optional scrape feedback.

On an authenticated session with Alexandria access, firecrawl_search with sources unset and firecrawl_find_tools can discover providers for the same fields across several pages; a matching provider returns typed records in one call. Keyless sessions have no provider matches.

Alexandria mode, on an authenticated session with Alexandria access: alexandria selects catalogued capability execution and is mutually exclusive with url.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "firecrawl_scrape"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
proxyNo
maxAgeNo
mobileNo
actionsNo
formatsNo
parsersNo
profileNo
timeoutNoExecution timeout in milliseconds.
waitForNo
locationNo
lockdownNo
redactPIINo
requestIdNoIdempotency key bound to one Alexandria execution payload. Generated when omitted and returned with the result.
alexandriaNoCatalogued Alexandria capability invocation, mutually exclusive with url. One {provider, capability, options} object or an array of 1-10, with contracts available through firecrawl_search or firecrawl_find_tools. Each call may include version to pin a published workflow; omitting it uses latest. Only requestId and timeout are supported alongside alexandria. The selected contract marks required inputs and any requiresOneOf groups (at least one member per group); it may include example.request/example.response and response.key (which may differ from records). Where pagination is declared, its fields govern paging with the same filters; catalogue next is separate from provider pagination. Returns per-capability results in data.alexandria with data, records, or an error with a code; individual capabilities can fail even when the outer response succeeds. Requires an API key on a team with Alexandria enabled. Some providers require accepted terms; blocked requests return the applicable requirements.
pdfOptionsNo
toolDetailNoURL mode only: domain discovery detail, summary by default; compact returns provider/capability/description, full includes contracts. Ignored with alexandria.
domainToolsNoURL mode only: include domain-matched Alexandria tools for the page in tools on the returned document. Ignored with alexandria.
excludeTagsNo
includeTagsNo
jsonOptionsNo
queryOptionsNo
storeInCacheNo
onlyMainContentNo
screenshotOptionsNo
zeroDataRetentionNo
removeBase64ImagesNo
skipTlsVerificationNo

Output Schema

NameRequiredDescriptionDefault
dataNoAlexandria mode: per-capability results in `data.alexandria`, each with `data`, `records`, or an `error`.
htmlNoProcessed HTML of the page.
jsonNoStructured data matching the requested JSON schema or prompt.
menuNoMenu data extracted from the page.
audioNoAudio extracted from the page.
errorNoError message or error object when the call did not succeed.
linksNoLinks found on the page.
pagesNoPhysical PDF pages, when `parsers[].pages` is set.
toolsNoDomain-matched Alexandria tools for the page, when `domainTools` is set.
videoNoVideo extracted from the page.
answerNoTargeted answer to the question that was asked of the page.
blocksNoTyped PDF layout blocks, when `parsers[].blocks` is set.
imagesNoImages found on the page.
actionsNoResults of the browser actions that ran during the scrape.
messageNoGuidance that accompanies the result.
productNoProduct data extracted from the page.
rawHtmlNoUnprocessed HTML of the page.
receiptNoBilling receipt for the execution.
successNoWhether the API call succeeded.
summaryNoSummary of the page content.
warningNoNon-fatal warning about the result.
brandingNoBranding data extracted from the page.
deliveryNo`retained` when the full result stayed server-side instead of being inlined.
markdownNoPage content as markdown.
metadataNoPage metadata; authenticated responses can include `metadata.scrapeId` for scrape feedback.
nextToolNoA follow-up tool call (`{name, arguments}`) that continues or inspects this result.
requestIdNoIdentifier of this Alexandria execution.
scrape_idNoIdentifier of the underlying scrape.
attributesNoValues collected by the requested attribute selectors.
highlightsNoHighlighted passages from the page.
screenshotNoScreenshot of the page.
agent_hintsNoOptional response guidance from the Firecrawl API.
creditsCostNoCredits this call consumed.
workspaceIdNoWorkspace holding a retained result, for inspection through virtual Bash.
feedbackToolNoPointer to the feedback tool for reporting how this result served the task.
responseBytesNoSize of the full result in bytes.
changeTrackingNoChange-tracking comparison against the previous scrape.
idleTtlSecondsNoSeconds a retained workspace stays available while idle.
estimatedTokensNoEstimated token cost of the full result.
inlineTokenBudgetNoToken budget above which a result is retained rather than inlined.
tokenEstimateMethodNoHow `estimatedTokens` was derived.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.28.2

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses staleness behavior, the `maxAge: 0` live-fetch option, the fact that browser actions can change the live page, authenticated-session metadata such as `metadata.scrapeId`, and keyless-session limitations. It also explains Alexandria mode prerequisites and mutual exclusivity with `url`, which materially affects how an agent should invoke the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and usage guidance, and its length is largely justified by the tool's many modes and caveats. It is still dense and somewhat repetitive around Alexandria/provider discovery, and clearer grouping of URL-mode versus Alexandria-mode details would improve scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the major decision points, safety-relevant behavior, staleness caveats, and Alexandria mode, and an output schema exists so return values need not be explained. But for a 28-parameter tool with very low schema description coverage, many optional parameters and their effects are left undocumented, leaving meaningful gaps for advanced invocations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds useful meaning for some key parameters, including `maxAge`, `actions`, `formats`, `alexandria`, `toolDetail`, `domainTools`, and authenticated scrape feedback. However, with 28 parameters and only 18% schema description coverage, many options such as `proxy`, `mobile`, `parsers`, `profile`, `waitFor`, `location`, `lockdown`, `redactPII`, content filters, screenshot options, and cache/retention settings remain unexplained, so it does not fully compensate for the low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: "Scrape one URL and return its content," and enumerates the return forms including markdown, HTML, links, screenshots, branding, answer, and JSON. It explicitly distinguishes the tool from `firecrawl_search`, `firecrawl_map`, and `firecrawl_crawl`, so an agent can identify its role without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-to-use rule: "Use it when the request identifies a page and needs its content or defined fields." It also names alternatives and their selection conditions, including `firecrawl_search` for additional sources, `firecrawl_map` for URL listing, `firecrawl_crawl` for page sets, and Alexandria mode for catalogued capability execution.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.