Skip to main content
Glama

Firecrawl MCP Server

firecrawl_search

Read-only

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". 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.

Input Schema

TableJSON 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
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. `developer` returns hits in `data.web` with `category: "developer"`; 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.
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

TableJSON 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 observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover read-only/open-world safety, but the description goes further: keyless vs authenticated behavior diverges (no Alexandria matches), default sources differ by session, scrapeOptions fetches ignore maxAge, and an optional search-feedback id is returned. These auth- and session-dependent traits are not derivable from annotations or schema.

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?

Dense but mostly front-loaded and every paragraph carries routing or auth information. Some Alexandria/tool-discovery detail is repeated across sentences (toolDetail vs firecrawl_find_tools appears twice), costing a little tightness.

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

Completeness5/5

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

For a 14-parameter, nested-schema, open-world search tool with an output schema, the description covers session-dependent defaults, provider-vs-scrape tradeoffs, category semantics, and return grouping without redundantly explaining the document-return schema.

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 only 64%, and the description meaningfully compensates for several under-documented params (sources defaults, domainTools defaults and web-only behavior, toolDetail compact/full semantics, categories including developer/research). It does defer operators and scrapeOptions to the parameter docs, which is reasonable since those are well-described in the schema.

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?

States a specific verb (search) and resource (web, news, image sources) plus the return shape (ranked results with highlights). It also distinguishes itself from firecrawl_scrape by naming when to use that sibling instead of this one.

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?

Explicit routing rules: use firecrawl_scrape when the excerpt is insufficient, prefer an Alexandria provider when the task spans several entities or needs exact figures, use web results when they already answer. Also explains sources/domainTools interactions and category selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.