Skip to main content
Glama
ashishdevthakur3-max

Firecrawl MCP Server

firecrawl_search

Search the web for specific information across multiple websites and extract content from search results to find relevant answers to queries.

Instructions

Search the web and optionally extract content from search results. This is the most powerful search tool available, and if available you should always default to using this tool for any web search needs.

Best for: Finding specific information across multiple websites, when you don't know which website has the information; when you need the most relevant content for a query. Not recommended for: When you already know which website to scrape (use scrape); when you need comprehensive coverage of a single website (use map or crawl). Common mistakes: Using crawl or map for open-ended questions (use search instead). Prompt Example: "Find the latest research papers on AI published in 2023." Usage Example:

{
  "name": "firecrawl_search",
  "arguments": {
    "query": "latest AI research papers 2023",
    "limit": 5,
    "lang": "en",
    "country": "us",
    "scrapeOptions": {
      "formats": ["markdown"],
      "onlyMainContent": true
    }
  }
}

Returns: Array of search results (with optional scraped content).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string
limitNoMaximum number of results to return (default: 5)
langNoLanguage code for search results (default: en)
countryNoCountry code for search results (default: us)
tbsNoTime-based search filter
filterNoSearch filter
locationNoLocation settings for search
scrapeOptionsNoOptions for scraping search results

Implementation Reference

  • The handler logic for 'firecrawl_search' which calls the client's search method and formats the results.
          case 'firecrawl_search': {
            if (!isSearchOptions(args)) {
              throw new Error('Invalid arguments for firecrawl_search');
            }
            try {
              const response = await withRetry(
                async () =>
                  client.search(args.query, { ...args, origin: 'mcp-server' }),
                'search operation'
              );
    
              if (!response.success) {
                throw new Error(
                  `Search failed: ${response.error || 'Unknown error'}`
                );
              }
    
              // Format the results
              const results = response.data
                .map(
                  (result) =>
                    `URL: ${result.url}
    Title: ${result.title || 'No title'}
    Description: ${result.description || 'No description'}
    ${result.markdown ? `\nContent:\n${result.markdown}` : ''}`
                )
                .join('\n\n');
    
              return {
                content: [{ type: 'text', text: trimResponseText(results) }],
                isError: false,
              };
            } catch (error) {
              const errorMessage =
                error instanceof Error
                  ? error.message
                  : `Search failed: ${JSON.stringify(error)}`;
              return {
                content: [{ type: 'text', text: trimResponseText(errorMessage) }],
                isError: true,
              };
            }
          }
  • The schema definition for the 'firecrawl_search' tool, including its input parameters and description.
    const SEARCH_TOOL: Tool = {
      name: 'firecrawl_search',
      description: `
    Search the web and optionally extract content from search results. This is the most powerful search tool available, and if available you should always default to using this tool for any web search needs.
    
    **Best for:** Finding specific information across multiple websites, when you don't know which website has the information; when you need the most relevant content for a query.
    **Not recommended for:** When you already know which website to scrape (use scrape); when you need comprehensive coverage of a single website (use map or crawl).
    **Common mistakes:** Using crawl or map for open-ended questions (use search instead).
    **Prompt Example:** "Find the latest research papers on AI published in 2023."
    **Usage Example:**
    \`\`\`json
    {
      "name": "firecrawl_search",
      "arguments": {
        "query": "latest AI research papers 2023",
        "limit": 5,
        "lang": "en",
        "country": "us",
        "scrapeOptions": {
          "formats": ["markdown"],
          "onlyMainContent": true
        }
      }
    }
    \`\`\`
    **Returns:** Array of search results (with optional scraped content).
    `,
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search query string',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of results to return (default: 5)',
          },
          lang: {
            type: 'string',
            description: 'Language code for search results (default: en)',
          },
          country: {
            type: 'string',
            description: 'Country code for search results (default: us)',
          },
          tbs: {
            type: 'string',
            description: 'Time-based search filter',
          },
          filter: {
            type: 'string',
            description: 'Search filter',
          },
          location: {
            type: 'object',
            properties: {
              country: {
                type: 'string',
                description: 'Country code for geolocation',
              },
              languages: {
                type: 'array',
                items: { type: 'string' },
                description: 'Language codes for content',
              },
            },
            description: 'Location settings for search',
          },
          scrapeOptions: {
            type: 'object',
            properties: {
              formats: {
                type: 'array',
                items: {
                  type: 'string',
                  enum: ['markdown', 'html', 'rawHtml'],
                },
                description: 'Content formats to extract from search results',
              },
              onlyMainContent: {
                type: 'boolean',
                description: 'Extract only the main content from results',
              },
              waitFor: {
                type: 'number',
                description: 'Time in milliseconds to wait for dynamic content',
              },
            },
            description: 'Options for scraping search results',
          },
        },
        required: ['query'],
      },
    };
  • src/index.ts:968-968 (registration)
    Registration of the 'firecrawl_search' tool in the list of available tools.
    SEARCH_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 the tool's capabilities (searching and optional extraction), power level ('most powerful search tool'), and return format ('Array of search results'). However, it doesn't mention rate limits, authentication needs, or potential costs, leaving some behavioral aspects unspecified.

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 clear sections (Best for, Not recommended for, Common mistakes, examples) and front-loads the core purpose. While comprehensive, some sections could be more concise, and the usage example is quite detailed, making it slightly longer than ideal.

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 complex tool with 8 parameters, nested objects, and no output schema, the description provides good context about usage scenarios and alternatives. However, it doesn't fully describe the return value structure beyond 'Array of search results', which could be more detailed given the lack of output schema.

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 thoroughly. The description adds minimal parameter semantics beyond the schema, mainly through the usage example showing typical values. It doesn't explain parameter interactions or provide additional context beyond what's in the schema descriptions.

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's purpose with specific verbs ('search the web', 'extract content') and resource ('search results'). It explicitly distinguishes this tool from sibling tools like scrape, map, and crawl by stating when to use each, making the purpose distinct and well-defined.

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 provides explicit guidance with 'Best for' and 'Not recommended for' sections, naming specific sibling tools (scrape, map, crawl) as alternatives. It includes a 'Common mistakes' section and states 'you should always default to using this tool for any web search needs', giving clear when-to-use rules.

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/ashishdevthakur3-max/firecrawl-mcp'

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