Skip to main content
Glama
firecrawl

firecrawl-mcp-server

firecrawl_scrape

Scrape content from a single web page with advanced options, supporting markdown, JSON schema-based extraction, and brand identity analysis.

Instructions

Scrape content from a single URL with advanced options. This is the most powerful, fastest and most reliable scraper tool, if available you should always default to using this tool for any web scraping needs.

Best for: Single page content extraction, when you know exactly which page contains the information. Not recommended for: Multiple pages (call scrape multiple times or use crawl), unknown page location (use search). Common mistakes: Using markdown format when extracting specific data points (use JSON instead). Other Features: Use 'branding' format to extract brand identity (colors, fonts, typography, spacing, UI components) for design analysis or style replication.

CRITICAL - Format Selection (you MUST follow this): When the user asks for SPECIFIC data points, you MUST use JSON format with a schema. Only use markdown when the user needs the ENTIRE page content.

Use JSON format when user asks for:

  • Parameters, fields, or specifications (e.g., "get the header parameters", "what are the required fields")

  • Prices, numbers, or structured data (e.g., "extract the pricing", "get the product details")

  • API details, endpoints, or technical specs (e.g., "find the authentication endpoint")

  • Lists of items or properties (e.g., "list the features", "get all the options")

  • Any specific piece of information from a page

Use markdown format ONLY when:

  • User wants to read/summarize an entire article or blog post

  • User needs to see all content on a page without specific extraction

  • User explicitly asks for the full page content

Handling JavaScript-rendered pages (SPAs): If JSON extraction returns empty, minimal, or just navigation content, the page is likely JavaScript-rendered or the content is on a different URL. Try these steps IN ORDER:

  1. Add waitFor parameter: Set waitFor: 5000 to waitFor: 10000 to allow JavaScript to render before extraction

  2. Try a different URL: If the URL has a hash fragment (#section), try the base URL or look for a direct page URL

  3. Use firecrawl_map to find the correct page: Large documentation sites or SPAs often spread content across multiple URLs. Use firecrawl_map with a search parameter to discover the specific page containing your target content, then scrape that URL directly. Example: If scraping "https://docs.example.com/reference" fails to find webhook parameters, use firecrawl_map with {"url": "https://docs.example.com/reference", "search": "webhook"} to find URLs like "/reference/webhook-events", then scrape that specific page.

  4. Use firecrawl_agent: As a last resort for heavily dynamic pages where map+scrape still fails, use the agent which can autonomously navigate and research

Usage Example (JSON format - REQUIRED for specific data extraction):

{
  "name": "firecrawl_scrape",
  "arguments": {
    "url": "https://example.com/api-docs",
    "formats": ["json"],
    "jsonOptions": {
      "prompt": "Extract the header parameters for the authentication endpoint",
      "schema": {
        "type": "object",
        "properties": {
          "parameters": {
            "type": "array",
            "items": {
              "type": "object",
              "properties": {
                "name": { "type": "string" },
                "type": { "type": "string" },
                "required": { "type": "boolean" },
                "description": { "type": "string" }
              }
            }
          }
        }
      }
    }
  }
}

Prefer markdown format by default. You can read and reason over the full page content directly — no need for an intermediate query step. Use markdown for questions about page content, factual lookups, and any task where you need to understand the page.

Use JSON format when user needs:

  • Structured data with specific fields (extract all products with name, price, description)

  • Data in a specific schema for downstream processing

Use query format only when:

  • The page is extremely long and you need a single targeted answer without processing the full content

  • You want a quick factual answer and don't need to retain the page content

  • Set queryOptions.mode to "directQuote" when you need verbatim page text; otherwise it defaults to "freeform"

Usage Example (markdown format - default for most tasks):

{
  "name": "firecrawl_scrape",
  "arguments": {
    "url": "https://example.com/article",
    "formats": ["markdown"],
    "onlyMainContent": true
  }
}

Usage Example (branding format - extract brand identity):

{
  "name": "firecrawl_scrape",
  "arguments": {
    "url": "https://example.com",
    "formats": ["branding"]
  }
}

Branding format: Extracts comprehensive brand identity (colors, fonts, typography, spacing, logo, UI components) for design analysis or style replication. Performance: Add maxAge parameter for 500% faster scrapes using cached data. Lockdown mode: Set lockdown: true to serve the request only from the existing index/cache without any outbound network request. For air-gapped or compliance-constrained use where the request URL itself is considered sensitive. Errors on cache miss. Billed at 5 credits. Privacy: Set redactPII: true to return content with personally identifiable information redacted. Returns: JSON structured data, markdown, branding profile, or other formats as specified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
proxyNo
maxAgeNo
mobileNo
actionsNo
formatsNo
parsersNo
profileNo
waitForNo
locationNo
lockdownNo
redactPIINo
pdfOptionsNo
excludeTagsNo
includeTagsNo
jsonOptionsNo
queryOptionsNo
storeInCacheNo
onlyMainContentNo
screenshotOptionsNo
zeroDataRetentionNo
removeBase64ImagesNo
skipTlsVerificationNo
Behavior4/5

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

Annotations only provide title, readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds significant behavioral context: performance with maxAge, lockdown mode (no outbound requests, cache-only), privacy redaction, JavaScript rendering handling with waitFor and retry strategies, and format-specific behaviors. It does not explicitly state it is read-only, but actions are implied to be non-destructive. The description covers most important traits beyond annotations, though it could be more structured.

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

Conciseness3/5

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

The description is very long and contains redundant instructions (e.g., format selection guidance appears twice). While it front-loads the main purpose and provides structured sections (Best for, Not recommended, Common mistakes, Critical, Handling JavaScript), the verbosity could be trimmed. Some information could be moved to separate documentation or example files. A more concise version would improve scanability.

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

Completeness4/5

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

Given the tool complexity (23 params, no output schema, nested objects), the description covers most critical aspects: when to use which format, how to handle JavaScript rendering, caching, privacy, and lockdown mode. It mentions return formats (JSON, markdown, branding) but does not detail the structure of each output type. Without an output schema, it could specify fields returned per format, but the examples partially fill this gap. Overall, it is comprehensive enough for effective tool selection and invocation.

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

Parameters4/5

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

The schema has 23 parameters with 0% coverage (no explicit descriptions in schema). The description compensates by explaining key parameters like formats (markdown, json, query, branding), waitFor, onlyMainContent, maxAge, lockdown, redactPII, actions, jsonOptions, and queryOptions in context. It provides usage examples and rules for format selection. However, some parameters like proxy, mobile, excludeTags, includeTags, screenshotOptions are not elaborated. Given the large parameter count, this is acceptable but not exhaustive.

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 clearly states the tool scrapes a single URL with advanced options. It distinguishes itself from siblings like crawl (multiple pages) and search (unknown page location), and emphasizes it is the most powerful and reliable scraper. The verb 'scrape' plus 'single URL' is specific and actionable.

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?

The description explicitly states best use cases (single page extraction) and not recommended scenarios (multiple pages, unknown location) with alternative tools. It provides common mistakes, critical format selection rules with examples, and a step-by-step approach for JavaScript-rendered pages. This leaves no ambiguity about when to invoke this tool versus siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/firecrawl/firecrawl-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server