Skip to main content
Glama
ai-integr8tor

Tavily MCP Server

tavily_crawl

Crawl a website starting from a root URL to extract content. Configure crawl depth, breadth, and target specific paths or domains.

Instructions

Crawl a website starting from a URL. Extracts content from pages with configurable depth and breadth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe root URL to begin the crawl
limitNoTotal number of links the crawler will process before stopping
formatNoThe format of the extracted web page content. markdown returns content in markdown format. text returns plain text and may increase latency.markdown
max_depthNoMax depth of the crawl. Defines how far from the base URL the crawler can explore.
max_breadthNoMax number of links to follow per level of the tree (i.e., per page)
instructionsNoNatural language instructions for the crawler. Instructions specify which types of pages the crawler should return.
select_pathsNoRegex patterns to select only URLs with specific path patterns (e.g., /docs/.*, /api/v1.*)
extract_depthNoAdvanced extraction retrieves more data, including tables and embedded content, with higher success but may increase latencybasic
allow_externalNoWhether to return external links in the final response
select_domainsNoRegex patterns to restrict crawling to specific domains or subdomains (e.g., ^docs\.example\.com$)
include_faviconNoWhether to include the favicon URL for each result
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only mentions 'crawl' and 'extracts content' with configurable depth and breadth. It omits details such as rate limits, respect for robots.txt, handling of dynamic content, or the nature of the extraction process. This is insufficient for safe invocation.

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?

The description is two sentences long, each serving a purpose: the first states the core action, the second adds key differentiators (configurable depth and breadth). No wasted words; highly efficient.

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

Completeness2/5

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

Despite having no output schema and 11 parameters, the description is extremely brief. It fails to explain return values, parameter effects (e.g., limit, max_depth), or operational behavior (e.g., whether it respects robots.txt). For a complex tool, this is insufficiently 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?

The input schema has 100% coverage with descriptions for all 11 parameters. Therefore, the baseline is 3. The description adds no additional meaning beyond what the schema provides, so no improvement or deduction.

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?

The description clearly states the verb 'crawl' and the resource 'a website starting from a URL', with added detail about extracting content and configurable depth/breadth. This distinguishes it from siblings like tavily_extract (which likely extracts specific data) and tavily_search, but it does not explicitly differentiate.

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?

No guidance on when to use this tool versus its siblings (tavily_extract, tavily_map, tavily_research, tavily_search). The description does not specify prerequisites, exclusion criteria, or alternative scenarios. The agent is left to infer usage from the tool name.

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/ai-integr8tor/tavily-mcp'

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