Skip to main content
Glama
NYO2008

Firecrawl MCP Server

by NYO2008

firecrawl_deep_research

Conduct deep web research on complex queries using intelligent crawling, search, and LLM analysis to generate comprehensive insights from multiple sources.

Instructions

Conduct deep web research on a query using intelligent crawling, search, and LLM analysis.

Best for: Complex research questions requiring multiple sources, in-depth analysis. Not recommended for: Simple questions that can be answered with a single search; when you need very specific information from a known page (use scrape); when you need results quickly (deep research can take time). Arguments:

  • query (string, required): The research question or topic to explore.

  • maxDepth (number, optional): Maximum recursive depth for crawling/search (default: 3).

  • timeLimit (number, optional): Time limit in seconds for the research session (default: 120).

  • maxUrls (number, optional): Maximum number of URLs to analyze (default: 50). Prompt Example: "Research the environmental impact of electric vehicles versus gasoline vehicles." Usage Example:

{
  "name": "firecrawl_deep_research",
  "arguments": {
    "query": "What are the environmental impacts of electric vehicles compared to gasoline vehicles?",
    "maxDepth": 3,
    "timeLimit": 120,
    "maxUrls": 50
  }
}

Returns: Final analysis generated by an LLM based on research. (data.finalAnalysis); may also include structured activities and sources used in the research process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe query to research
maxDepthNoMaximum depth of research iterations (1-10)
timeLimitNoTime limit in seconds (30-300)
maxUrlsNoMaximum number of URLs to analyze (1-1000)

Implementation Reference

  • Handler function that executes the firecrawl_deep_research tool by calling the Firecrawl client's deepResearch method with provided arguments, handling callbacks for activities and sources, logging performance, and formatting the final analysis response.
    case 'firecrawl_deep_research': {
      if (!args || typeof args !== 'object' || !('query' in args)) {
        throw new Error('Invalid arguments for firecrawl_deep_research');
      }
    
      try {
        const researchStartTime = Date.now();
        safeLog('info', `Starting deep research for query: ${args.query}`);
    
        const response = await client.deepResearch(
          args.query as string,
          {
            maxDepth: args.maxDepth as number,
            timeLimit: args.timeLimit as number,
            maxUrls: args.maxUrls as number,
            // @ts-expect-error Extended API options including origin
            origin: 'mcp-server',
          },
          // Activity callback
          (activity) => {
            safeLog(
              'info',
              `Research activity: ${activity.message} (Depth: ${activity.depth})`
            );
          },
          // Source callback
          (source) => {
            safeLog(
              'info',
              `Research source found: ${source.url}${source.title ? ` - ${source.title}` : ''}`
            );
          }
        );
    
        // Log performance metrics
        safeLog(
          'info',
          `Deep research completed in ${Date.now() - researchStartTime}ms`
        );
    
        if (!response.success) {
          throw new Error(response.error || 'Deep research failed');
        }
    
        // Format the results
        const formattedResponse = {
          finalAnalysis: response.data.finalAnalysis,
          activities: response.data.activities,
          sources: response.data.sources,
        };
    
        return {
          content: [
            {
              type: 'text',
              text: trimResponseText(formattedResponse.finalAnalysis),
            },
          ],
          isError: false,
        };
      } catch (error) {
        const errorMessage =
          error instanceof Error ? error.message : String(error);
        return {
          content: [{ type: 'text', text: trimResponseText(errorMessage) }],
          isError: true,
        };
      }
    }
  • Tool schema definition including name, detailed description, and inputSchema for validating arguments like query (required), maxDepth, timeLimit, maxUrls.
    const DEEP_RESEARCH_TOOL: Tool = {
      name: 'firecrawl_deep_research',
      description: `
    Conduct deep web research on a query using intelligent crawling, search, and LLM analysis.
    
    **Best for:** Complex research questions requiring multiple sources, in-depth analysis.
    **Not recommended for:** Simple questions that can be answered with a single search; when you need very specific information from a known page (use scrape); when you need results quickly (deep research can take time).
    **Arguments:**
    - query (string, required): The research question or topic to explore.
    - maxDepth (number, optional): Maximum recursive depth for crawling/search (default: 3).
    - timeLimit (number, optional): Time limit in seconds for the research session (default: 120).
    - maxUrls (number, optional): Maximum number of URLs to analyze (default: 50).
    **Prompt Example:** "Research the environmental impact of electric vehicles versus gasoline vehicles."
    **Usage Example:**
    \`\`\`json
    {
      "name": "firecrawl_deep_research",
      "arguments": {
        "query": "What are the environmental impacts of electric vehicles compared to gasoline vehicles?",
        "maxDepth": 3,
        "timeLimit": 120,
        "maxUrls": 50
      }
    }
    \`\`\`
    **Returns:** Final analysis generated by an LLM based on research. (data.finalAnalysis); may also include structured activities and sources used in the research process.
    `,
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'The query to research',
          },
          maxDepth: {
            type: 'number',
            description: 'Maximum depth of research iterations (1-10)',
          },
          timeLimit: {
            type: 'number',
            description: 'Time limit in seconds (30-300)',
          },
          maxUrls: {
            type: 'number',
            description: 'Maximum number of URLs to analyze (1-1000)',
          },
        },
        required: ['query'],
      },
    };
  • src/index.ts:955-966 (registration)
    Registers the firecrawl_deep_research tool (as DEEP_RESEARCH_TOOL) in the server's list of available tools returned by ListToolsRequestSchema.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        SCRAPE_TOOL,
        MAP_TOOL,
        CRAWL_TOOL,
        CHECK_CRAWL_STATUS_TOOL,
        SEARCH_TOOL,
        EXTRACT_TOOL,
        DEEP_RESEARCH_TOOL,
        GENERATE_LLMSTXT_TOOL,
      ],
    }));
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: it's a research tool that may take time ('deep research can take time'), involves multiple sources and LLM analysis, and returns a final analysis. However, it lacks details on potential errors, rate limits, or authentication needs, which could be relevant for an AI agent.

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 well-structured with sections like 'Best for:', 'Arguments:', and examples, making it easy to scan. It's appropriately sized, with each sentence adding value, though it could be slightly more concise by integrating some details more tightly.

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's complexity (deep research with multiple parameters) and no output schema, the description does a good job explaining the purpose, usage, and returns ('Final analysis generated by an LLM'). It covers key aspects but could benefit from more detail on output structure or error handling to be fully complete.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds default values (e.g., 'default: 3' for maxDepth) and a prompt example, providing some extra context, but doesn't significantly enhance meaning beyond what's in the schema. This meets the baseline for high 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 clearly states the tool 'conduct[s] deep web research on a query using intelligent crawling, search, and LLM analysis.' This specifies the verb ('conduct deep web research'), resource ('query'), and method ('crawling, search, and LLM analysis'), distinguishing it from siblings like 'scrape' or 'search' by emphasizing depth and analysis.

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 provides 'Best for:' and 'Not recommended for:' sections, detailing when to use this tool (complex research questions requiring multiple sources) versus alternatives (e.g., use 'scrape' for specific information from known pages). It also mentions time considerations, offering clear guidance on tool selection.

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/NYO2008/firecrawl-mcp-server'

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