Skip to main content
Glama
tavily-firecrawl-mcp

tavily-firecrawl-mcp

by bpzx

web_search

Search the web for titles, URLs, and snippets on general or news topics, with an optional answer and automatic fallback from Tavily to Firecrawl when needed.

Instructions

Search the web and return titles, URLs, and snippets. Tries Tavily first (optionally with a synthesized answer); on failure falls back to Firecrawl Search. Requires TAVILY_API_KEY and/or FIRECRAWL_API_KEY in the server's environment.

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": "web_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
topicNogeneral
max_resultsNo
search_depthNobasic
include_answerNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • addedInput schema / properties / search_depth / enum
      Added value: +[
      +  "basic",
      +  "advanced"
      +]
    • addedInput schema / properties / topic / enum
      Added value: +[
      +  "general",
      +  "news"
      +]
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the provider fallback chain (Tavily first, Firecrawl Search on failure), that an optional synthesized answer may be returned, and the required environment credentials. Gaps remain around what happens when both providers fail, rate limits, and cost/latency characteristics.

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?

Three sentences, front-loaded with the core action and return content before provider and credential details. Nothing is redundant, though the provider internals are close to implementation detail rather than caller-facing information.

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

Completeness3/5

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

An output schema exists, so return values need not be re-explained, and the credential/fallback context is valuable. However, with 0% schema coverage on five parameters, the definition leaves three tuning parameters (topic, max_results, search_depth) unexplained, which is a real gap for an agent choosing values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must compensate. It only clarifies one of them ('optionally with a synthesized answer' maps to include_answer); topic, max_results, and search_depth are left entirely to bare enum/default definitions with no explanation of their effect.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the web') plus the return shape ('titles, URLs, and snippets'), which implicitly separates it from the sibling web_fetch that retrieves a known URL. It stops short of naming the sibling or explicitly excluding the fetch-a-specific-URL case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no mention of web_fetch as the alternative for retrieving a known page. The provider-fallback sentence describes internal mechanics rather than routing advice, leaving the agent to infer that this is the discovery tool and web_fetch the retrieval tool.

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

Deploy Server

Other Tools