Skip to main content
Glama
Sign In
Tavily Web Search MCP Server

Tavily Web Search MCP Server

by bakshidwarak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

web_search

Search the web for information using natural language queries to find answers and data from the internet.

Instructions

Search the web for information about the given query

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": {
      "query": "<query>"
    },
    "name": "web_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • server.py:12-16 (handler)
    The handler function for the 'web_search' tool, decorated with @mcp.tool() for registration. It takes a query string, uses the global TavilyClient to perform the search, and returns the search results.
    @mcp.tool()
def web_search(query: str) -> str:
    """Search the web for information about the given query"""
    search_results = client.get_search_context(query=query)
    return search_results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"web_searchArguments"
  2. First observed

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'search the web' without explaining what the tool returns, any limitations (e.g., freshness, pagination), or side effects. This lack of detail leaves the agent uncertain about the tool's behavior beyond the obvious.

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 a single sentence, ten words long, and front-loaded with the core action. There is no wasted text or redundancy. It is appropriately concise for a simple tool, and every word earns its place.

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?

The tool is low-complexity with one parameter and no output schema. The description fails to explain the return value, result format, or any constraints/edge cases. Since there is no output schema, the description should cover what the agent can expect after invocation, but it does not. This makes the description incomplete for an agent to use correctly.

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?

The schema has one parameter 'query' with a string type, and the description mentions 'the given query,' which is redundant. Since schema description coverage is 0%, the description should add meaning about the query format, examples, or constraints, but it does not. The parameter is self-explanatory, but the description adds no extra value.

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 tool's function: 'Search the web for information about the given query.' It uses a specific verb ('search') and resource ('web'), and the query is self-evident. While it doesn't explicitly distinguish from siblings, the only sibling is 'roll_dice,' which is clearly unrelated, so no differentiation is needed.

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 usage: use this tool when you need web information. However, it provides no explicit guidance on when to prefer this tool over alternatives, when not to use it, or any prerequisites. There is no mention of exclusions or comparison with the sibling tool, so it remains at an implied level.

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