Skip to main content
Glama
tavily-firecrawl-mcp

tavily-firecrawl-mcp

by bpzx

web_fetch

Fetch and extract a web page as markdown or plain text, with automatic fallback so content retrieval succeeds when the first provider fails or returns nothing.

Instructions

Fetch and extract the content of a web page as markdown (or plain text). Tries Tavily first; on failure or empty result, automatically falls back to Firecrawl. 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": {
      "url": "<url>"
    },
    "name": "web_fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
queryNo
formatNomarkdown
timeoutNo
extract_depthNobasic
only_main_contentNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • addedInput schema / properties / extract_depth / enum
      Added value: +[
      +  "basic",
      +  "advanced"
      +]
    • addedInput schema / properties / format / enum
      Added value: +[
      +  "markdown",
      +  "text"
      +]
  2. First observedv0.1.0

TDQS

A3.8/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 disclose the key operational trait: a two-provider chain (Tavily first, Firecrawl fallback on failure or empty result) and the required environment keys. It omits what happens when both providers fail and any notes on rate limits or truncation of long pages.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: capability and output format first, fallback behavior and auth requirements second. No filler and nothing buried.

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 explained, and the auth/fallback story is covered. However, for a six-parameter tool with zero schema coverage the definition leaves too many parameters and the total-failure case undocumented.

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 six parameters, so the description must compensate, yet it only hints at 'format' (markdown/text). Nothing is said about query, timeout, extract_depth, or only_main_content, leaving four of six parameters with no explanation anywhere.

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+resource ('Fetch and extract the content of a web page') plus the return format (markdown or plain text), which makes it clearly distinct from the sibling web_search tool that finds pages rather than retrieving a known URL.

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

Usage Guidelines3/5

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

The description implies the trigger (you have a URL and want its content), but never says explicitly when to use this instead of web_search, nor any exclusions such as non-HTML resources or authenticated pages.

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