Skip to main content
Glama

tavily-search

Search the web for real-time information and news using customizable filters for content type, domains, and time ranges to gather relevant results.

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
queryYesSearch query
search_depthNoThe depth of the search. It can be 'basic' or 'advanced'basic
topicNoThe category of the search. This will determine which of our agents will be used for the searchgeneral
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
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
include_imagesNoInclude a list of query-related images in the response
include_image_descriptionsNoInclude a list of query-related images and their descriptions in the response
include_raw_contentNoInclude the cleaned and parsed HTML content of each search result
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
exclude_domainsNoList of domains to specifically exclude, if the user asks to exclude a domain set this to the domain of the site

Implementation Reference

  • Core handler function that executes the tavily-search tool by making an API call to Tavily's search endpoint with the provided parameters.
    async search(params: any): Promise<TavilyResponse> {
      try {
        // Choose endpoint based on whether it's an extract request
        const endpoint = params.url ? this.baseURLs.extract : this.baseURLs.search;
        
        // Add topic: "news" if query contains the word "news"
        const searchParams = {
          ...params,
          api_key: API_KEY,
          topic: params.query.toLowerCase().includes('news') ? 'news' : undefined
        };
        
        const response = await this.axiosInstance.post(endpoint, searchParams);
        return response.data;
      } catch (error: any) {
        if (error.response?.status === 401) {
          throw new Error('Invalid API key');
        } else if (error.response?.status === 429) {
          throw new Error('Usage limit exceeded');
        }
        throw error;
      }
    }
  • Input schema definition for the tavily-search tool, specifying parameters, types, descriptions, defaults, and requirements.
    inputSchema: {
      type: "object",
      properties: {
        query: { 
          type: "string", 
          description: "Search query" 
        },
        search_depth: {
          type: "string",
          enum: ["basic","advanced"],
          description: "The depth of the search. It can be 'basic' or 'advanced'",
          default: "basic"
        },
        topic : {
          type: "string",
          enum: ["general","news"],
          description: "The category of the search. This will determine which of our agents will be used for the search",
          default: "general"
        },
        days: {
          type: "number",
          description: "The 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",
          default: 3
        },
        time_range: {
          type: "string",
          description: "The time range back from the current date to include in the search results. This feature is available for both 'general' and 'news' search topics",
          enum: ["day", "week", "month", "year", "d", "w", "m", "y"],
        },
        max_results: { 
          type: "number", 
          description: "The maximum number of search results to return",
          default: 10,
          minimum: 5,
          maximum: 20
        },
        include_images: { 
          type: "boolean", 
          description: "Include a list of query-related images in the response",
          default: false,
        },
        include_image_descriptions: { 
          type: "boolean", 
          description: "Include a list of query-related images and their descriptions in the response",
          default: false,
        },
        /*
        // Since the mcp server is using claude to generate answers form the search results, we don't need to include this feature.
        include_answer: { 
          type: ["boolean", "string"],
          enum: [true, false, "basic", "advanced"],
          description: "Include an answer to original query, generated by an LLM based on Tavily's search results. Can be boolean or string ('basic'/'advanced'). 'basic'/true answer will be quick but less detailed, 'advanced' answer will be more detailed but take longer to generate",
          default: false,
        },
        */
        include_raw_content: { 
          type: "boolean", 
          description: "Include the cleaned and parsed HTML content of each search result",
          default: false,
        },
        include_domains: {
          type: "array",
          items: { type: "string" },
          description: "A 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",
          default: []
        },
        exclude_domains: {
          type: "array",
          items: { type: "string" },
          description: "List of domains to specifically exclude, if the user asks to exclude a domain set this to the domain of the site",
          default: []
        }
      },
      required: ["query"]
  • src/index.ts:92-170 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining name, description, and inputSchema for tavily-search.
    {
      name: "tavily-search",
      description: "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.",
      inputSchema: {
        type: "object",
        properties: {
          query: { 
            type: "string", 
            description: "Search query" 
          },
          search_depth: {
            type: "string",
            enum: ["basic","advanced"],
            description: "The depth of the search. It can be 'basic' or 'advanced'",
            default: "basic"
          },
          topic : {
            type: "string",
            enum: ["general","news"],
            description: "The category of the search. This will determine which of our agents will be used for the search",
            default: "general"
          },
          days: {
            type: "number",
            description: "The 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",
            default: 3
          },
          time_range: {
            type: "string",
            description: "The time range back from the current date to include in the search results. This feature is available for both 'general' and 'news' search topics",
            enum: ["day", "week", "month", "year", "d", "w", "m", "y"],
          },
          max_results: { 
            type: "number", 
            description: "The maximum number of search results to return",
            default: 10,
            minimum: 5,
            maximum: 20
          },
          include_images: { 
            type: "boolean", 
            description: "Include a list of query-related images in the response",
            default: false,
          },
          include_image_descriptions: { 
            type: "boolean", 
            description: "Include a list of query-related images and their descriptions in the response",
            default: false,
          },
          /*
          // Since the mcp server is using claude to generate answers form the search results, we don't need to include this feature.
          include_answer: { 
            type: ["boolean", "string"],
            enum: [true, false, "basic", "advanced"],
            description: "Include an answer to original query, generated by an LLM based on Tavily's search results. Can be boolean or string ('basic'/'advanced'). 'basic'/true answer will be quick but less detailed, 'advanced' answer will be more detailed but take longer to generate",
            default: false,
          },
          */
          include_raw_content: { 
            type: "boolean", 
            description: "Include the cleaned and parsed HTML content of each search result",
            default: false,
          },
          include_domains: {
            type: "array",
            items: { type: "string" },
            description: "A 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",
            default: []
          },
          exclude_domains: {
            type: "array",
            items: { type: "string" },
            description: "List of domains to specifically exclude, if the user asks to exclude a domain set this to the domain of the site",
            default: []
          }
        },
        required: ["query"]
      }
    },
  • Dispatch case in CallToolRequestSchema handler that invokes the search method for tavily-search with parsed arguments.
    case "tavily-search":
      response = await this.search({
        query: args.query,
        search_depth: args.search_depth,
        topic: args.topic,
        days: args.days,
        time_range: args.time_range,
        max_results: args.max_results,
        include_images: args.include_images,
        include_image_descriptions: args.include_image_descriptions,
        include_raw_content: args.include_raw_content,
        include_domains: Array.isArray(args.include_domains) ? args.include_domains : [],
        exclude_domains: Array.isArray(args.exclude_domains) ? args.exclude_domains : []
      });
  • Helper function to format the Tavily API response into a readable text output for the tool response.
    function formatResults(response: TavilyResponse): string {
      // Format API response into human-readable text
      const output: string[] = [];
    
      // Include answer if available
      if (response.answer) {
        output.push(`Answer: ${response.answer}`);
        output.push('\nSources:');
        response.results.forEach(result => {
          output.push(`- ${result.title}: ${result.url}`);
        });
        output.push('');
      }
    
      // Format detailed search results
      output.push('Detailed Results:');
      response.results.forEach(result => {
        output.push(`\nTitle: ${result.title}`);
        output.push(`URL: ${result.url}`);
        output.push(`Content: ${result.content}`);
        if (result.raw_content) {
          output.push(`Raw Content: ${result.raw_content}`);
        }
      });
    
      return output.join('\n');
    }
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 the tool is 'powerful' and provides 'real-time results', but lacks details on rate limits, authentication needs, error handling, or response format. It partially compensates by noting it's for 'current information' and 'analysis', but behavioral traits are not fully disclosed.

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?

The description is appropriately sized and front-loaded, starting with the core function and key features. It uses three sentences efficiently, though the last sentence could be slightly more concise by integrating 'Ideal for' into the preceding context.

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?

Given the complexity (11 parameters, no annotations, no output schema), the description is moderately complete. It covers the purpose and high-level usage but lacks details on behavioral aspects like rate limits or output structure, which are important for a search tool with many parameters.

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 schema description coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema by mentioning 'customizable parameters for result count, content type, and domain filtering', but does not elaborate on parameter interactions or provide additional semantic context not already in the schema descriptions.

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 the tool performs web search using Tavily's AI engine, specifying it returns comprehensive, real-time results with customizable parameters. It distinguishes itself from the sibling tool 'tavily-extract' by focusing on search rather than extraction, though the sibling's function isn't detailed here.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool ('gathering current information, news, and detailed web content analysis'), but does not explicitly state when not to use it or mention alternatives like the sibling tool 'tavily-extract' for comparison.

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

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