Firecrawl Deep Research

Adapt the investigation to the question and the evidence available. This plugin uses Firecrawl's search MCP connection, not the full suite. Resolve deferred tools through the host's tool discovery when needed and follow the live schemas; use only operations exposed by this connection. Never invent tools or translate CLI flags into tool arguments.

Frame the investigation

Prefer a focused workflow when it can complete the request, such as enrich-lead for supplied people or lead CSVs, find-leads for new prospects, business-contact-research for published organizational contacts, or read-docs for official documentation. Use deep research for broader cross-source synthesis; multiple records or tool calls alone do not require it. Keep reusable evidence when switching workflows.

Invocation does not require an exhaustive investigation. Start with the smallest useful retrieval and expand only for gaps that could change the answer. Do not start paid enrichment merely because this skill is active. Use it when the requested scope and missing evidence justify it; keep simple answers simple.

Infer scope, dates, geography, audience and output; ask only for decisions that materially change the investigation. Convert relative dates to explicit bounds. For substantial investigations, briefly state the main questions, evidence routes, then begin. Revise the questions as findings reveal consequential gaps or competing explanations.

Use firecrawl_search with the actual question and its constraints to find sources, or the dedicated method below when the evidence calls for it, such as papers, code or US law. Read supplied URLs with firecrawl_scrape. Inspect relevant page results and matching capability suggestions returned by search.

When firecrawl_search exposes objective, set it to [deep-research] followed by the broader research goal, keeping that goal consistent across related searches. Keep query focused on the specific evidence needed, without the marker. Omit objective if the live schema does not support it, and avoid sensitive information in the goal.

Respect user-specified time, credit, page and result limits and returned account or tool restrictions. Do not impose default budgets, source quotas or minimum call counts; stop collecting when the requested answer is supported.

When the user sets a credit cap, track returned usage across calls. Count aggregate receipts and their included charges only once. Missing usage is unknown, not zero. Stop paid collection if the remaining budget cannot be established or respected.