Skip to main content
Glama

Firecrawl web search

firecrawl_search
Read-only

Search web, news, or image sources and return ranked results with query-relevant highlights; optionally fetch page content for web results.

Instructions

Search web, news, or image sources and return ranked results with query-relevant highlights. Each web result is a title, URL, and description; use firecrawl_scrape on a result URL when the excerpt is not enough.

Authenticated search also returns matching Alexandria data providers in data.tools (companies, people, jobs, finance and filings, public records and government spending, real estate, places and restaurants, retail and prices, package registries and developer data, news, research, and more). Prefer a provider over scraping pages when the task needs the same fields across several entities, exact figures or timestamps, provenance, or many records; use web results when they already answer the question. A search with sources: ["web"] omits semantic provider discovery; domainTools: true can still return website-matched tools. Web-only results use domainTools: false.

On an authenticated session, tool matches describe available capabilities; firecrawl_find_tools returns their contracts and firecrawl_scrape with an alexandria body executes a selected capability. Keyless sessions get no Alexandria matches in data.tools.

For a programming question, add categories: ["developer"]; its hits return in data.web with category: "developer". For a legal or regulatory question, categories: ["gov"] returns hits in data.web with category: "gov" and cannot be combined with other categories; authenticated sessions also have firecrawl_gov_search as the dedicated tool. categories: ["research"] restricts web results to research-affiliated websites; the firecrawl_research_* tools are a separate surface over paper abstracts and full text (PubMed, bioRxiv, medRxiv, arXiv). Query operators, domain filters, categories, toolDetail and scrapeOptions are described on their parameters. Returns source-type result groups and usage metadata. Authenticated responses can include an id for optional search feedback.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "firecrawl_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tbsNo
limitNo
queryYesQuery for web and semantic tool discovery. Operators include quoted phrases, `-term`, `site:host`, `inurl:term`, `intitle:term`, and `related:host`; the set is non-exhaustive. Catalogue browsing is available through firecrawl_find_tools.
filterNo
sourcesNoSearch sources; authenticated sessions default to web + alexandria, keyless sessions to web only. A search with sources: ["web"] omits semantic provider discovery; domainTools: true can still return website-matched tools. Web-only results use domainTools: false. Use ["alexandria"] alone for provider discovery without web results.
locationNo
objectiveNoOptional broader goal for this search, if known. Avoid sensitive information.
categoriesNoLimit results to specific source types. `research` restricts ordinary web results to research-affiliated websites and returns page snippets, which is separate from the `firecrawl_research_*` tools that search paper abstracts and full text across biomedical (PubMed, bioRxiv, medRxiv) and arXiv literature; `pdf` searches PDF results; `developer` searches an index built for coding agents over public repositories, GitHub issues, merged pull requests, repository READMEs, and code documentation; `gov` searches the Government Index of US federal, state, and local legal and regulatory sources, the index behind firecrawl_gov_search, and cannot be combined with other categories. `developer` and `gov` return hits in `data.web` with `category` set to their name; the other categories also filter `data.web`.
enterpriseNo
highlightsNoReturn query-relevant page excerpts for web and news results when available (default). Highlights appear in web `description` and news `snippet`; otherwise, original snippets are returned. Set to false to keep the original search snippets.
toolDetailNoCompact by default. Compact returns only provider, capability and description; full includes contracts. Inspect selected compact tools with firecrawl_find_tools providers and capabilities.
clientModelNoOptional model identifier, if known.
domainToolsNoInclude domain-matched tools for result URLs. Defaults to true when Alexandria is combined with web, news or images; semantic-only search leaves domain matching off.
scrapeOptionsNoAttach page content for web results in the same call. These fetches ignore maxAge, so use firecrawl_scrape when you need a live fetch. scrapeOptions fetches web pages, never Alexandria provider tools.
excludeDomainsNoHostnames to leave out of results. Mutually exclusive with includeDomains.
includeDomainsNoHostnames to restrict results to. Mutually exclusive with excludeDomains.

Output Schema

NameRequiredDescriptionDefault
idNoSearch identifier, for optional `firecrawl_search_feedback`.
dataNoRanked results grouped by source, such as `web`, `news`, `images`, and `alexandria`.
errorNoError message or error object when the call did not succeed.
toolsNoDomain-matched Alexandria tools for the results.
successNoWhether the API call succeeded.
warningNoNon-fatal warning about the result.
nextToolNoA follow-up tool call that continues this search.
agent_hintsNoOptional response guidance from the Firecrawl API.
creditsUsedNoCredits this search consumed.
feedbackToolNoPointer to the feedback tool for this search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.28.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, yet the description adds real behavioural context beyond them: authenticated vs keyless session differences in data.tools, default source sets per session type, domainTools defaulting rules, the mutual exclusivity of the gov category, and that authenticated responses may include an id for optional feedback. This is materially more than the annotations supply.

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?

Front-loaded with purpose and follow-up advice, which is good, but the middle section is dense and partly redundant – the sources:["web"] / domainTools interaction is stated in both the description and the schema's sources description, and the categories paragraph restates schema text nearly verbatim. The Alexandria session paragraph is long and could be tightened considerably without losing information.

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?

For a 16-parameter tool with nested scrapeOptions and an output schema present, the description covers the complications an agent would otherwise get wrong: auth-dependent defaults, category exclusivity, and the Alexandria/scrape handoff. Return value detail is correctly omitted because an output schema exists, though several optional parameters remain unexplained in prose.

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?

Schema coverage is 69%, and the description still adds meaning on top: default source composition per session, the interaction between sources:["web"] and domainTools, toolDetail's compact default, and highlighting defaults. A few parameters (tbs, filter, location, enterprise, clientModel) are left entirely to the schema, which slightly caps this score.

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?

Opens with a specific verb and resource set ('Search web, news, or image sources and return ranked results with query-relevant highlights') and immediately differentiates from siblings by naming firecrawl_scrape for follow-up. The agent can tell what this does and how it differs from firecrawl_find_tools, firecrawl_gov_search, and the firecrawl_research_* tools without opening any 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?

Gives explicit when-to-use guidance with alternatives: prefer an Alexandria provider when the task needs the same fields across several entities, exact figures, provenance, or many records, and use web results when they already answer the question. It also routes specific query classes to firecrawl_gov_search, firecrawl_research_*, firecrawl_find_tools, and firecrawl_scrape, plus exclusions such as gov not combining with other categories.

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