Skip to main content
Glama
online111111

Tavily Search MCP Server

by online111111

tavily_search

Search the internet for up-to-date information using automatic API key rotation to manage rate limits.

Instructions

搜索互联网获取最新信息。多 API Key 自动轮换,配额耗尽时自动切换。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
search_depthNobasic
topicNogeneral
time_rangeNo
start_dateNo
end_dateNo
daysNo
max_resultsNo
include_answerNo
include_imagesNo
include_raw_contentNo
include_faviconNo
include_usageNo
auto_parametersNo
exact_matchNo
countryNo
include_domainsNo
exclude_domainsNo
timeoutNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries burden. It discloses auto-rotation of API keys and quota exhaustion handling, adding useful behavioral context. However, it does not mention rate limits, cost implications, or behavior when all keys are exhausted.

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?

Two sentences, front-loaded with purpose, then behavioral trait. No wasted words. Efficient and concise.

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 an output schema, the description lacks details on the many parameters (e.g., search_depth, topic, time_range). With 19 parameters, this is insufficient for an agent to use effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for 19 parameters; description adds no explanation of any parameter meanings. The burden on description to compensate is high, but it fails entirely.

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?

Description clearly states it searches the internet for latest information, using a specific verb and resource. However, it does not differentiate from sibling tool 'tavily_search_context', which likely has overlapping functionality.

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 alternatives like 'tavily_search_context' or 'tavily_extract'. The description lacks context about prerequisites or exclusions.

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/online111111/tavily-search-mcp-server'

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