Skip to main content
Glama

tavily-search

Search the web for real-time, relevant content using AI. Customize with parameters for depth, topic, dates, domains, and more.

Instructions

A powerful web search tool that provides comprehensive, real-time results using Tavily's AI search engine. Returns relevant web content with customizable parameters for result count, content type, and domain filtering. Ideal for gathering current information, news, and detailed web content analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoThe number of days back from the current date to include in the search results. This specifies the time frame of data to be retrieved. Please note that this feature is only available when using the 'news' search topic
queryYesSearch query
topicNoThe category of the search. This will determine which of our agents will be used for the searchgeneral
countryNoBoost search results from a specific country. This will prioritize content from the selected country in the search results. Available only if topic is general. Country names MUST be written in lowercase, plain English, with spaces and no underscores.
end_dateNoWill return all results before the specified end date. Required to be written in the format YYYY-MM-DD
start_dateNoWill return all results after the specified start date. Required to be written in the format YYYY-MM-DD.
time_rangeNoThe time range back from the current date to include in the search results. This feature is available for both 'general' and 'news' search topics
max_resultsNoThe maximum number of search results to return
search_depthNoThe depth of the search. It can be 'basic' or 'advanced'basic
include_imagesNoInclude a list of query-related images in the response
exclude_domainsNoList of domains to specifically exclude, if the user asks to exclude a domain set this to the domain of the site
include_domainsNoA list of domains to specifically include in the search results, if the user asks to search on specific sites set this to the domain of the site
include_faviconNoWhether to include the favicon URL for each result
include_raw_contentNoInclude the cleaned and parsed HTML content of each search result
include_image_descriptionsNoInclude a list of query-related images and their descriptions in the response
Behavior3/5

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

With no annotations provided, the description carries the full burden. It mentions 'real-time results' and 'customizable parameters' but omits important behavioral traits such as rate limits, result count limits, pagination, or whether the operation is read-only. The description implies a read operation but does not explicitly state it.

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, front-loaded with the primary purpose, and each sentence contributes value without repetition 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?

For a tool with 15 parameters and no output schema, the description is somewhat brief. It gives a high-level overview but lacks details on return format, result structure, or pagination behavior. The description is adequate but not comprehensive.

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. The description adds general context by summarizing parameter categories (result count, content type, domain filtering), but does not provide additional meaning beyond what is in the schema.

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 identifies the tool as a web search tool with real-time results and customizable parameters. However, it does not distinguish it from sibling tools like tavily-crawl, tavily-extract, or tavily-map, which may also perform web content retrieval.

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 explicit guidance on when to use this tool versus alternatives. The description states it is 'ideal for gathering current information, news, and detailed web content analysis,' but does not specify when to avoid it or mention any exclusions or prerequisites.

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/BACH-AI-Tools/tavily-mcp'

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