Skip to main content
Glama
pzehrel

tavily-proxy-mcp

by pzehrel

tavily_crawl

Read-only

Crawl websites starting from a URL, extracting page content with configurable depth and breadth. Filter by paths, domains, or natural language instructions.

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds no extra behavioral context such as crawl limits, latency, robots.txt handling, or result pagination. The mention of 'depth and breadth' simply reflects parameter semantics, not behavior.

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 exceptionally concise—two short sentences that immediately convey the tool's core function. No redundant words or fluff.

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?

Despite having 11 parameters and a related output schema, the description offers only a high-level overview. It does not discuss configuration scenarios, limitations, or typical use cases. The thorough schema and output schema partially compensate, but the description alone is insufficient for an agent to understand the tool's full range and trade-offs.

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 descriptive parameter definitions (e.g., limit, format, max_depth). The description adds no additional meaning beyond what the schema provides, so the baseline 3 applies.

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 a specific action ('Crawl a website starting from a URL') with a clear resource and scope. It also mentions extract content and configurable depth/breadth, distinguishing it from sibling tools like tavily_search and tavily_extract.

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 tool is for full-site crawling from a root URL, but does not explicitly state when to prefer it over alternatives such as tavily_extract or tavily_search. No exclusions or 'when-not-to-use' guidance is provided.

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/pzehrel/tavily-proxy-mcp'

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