Tavily Web Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAVILY_API_KEY | Yes | Your Tavily API key for web search capabilities |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchC | Search the web for information about the given query |
| roll_diceC | Roll the dice with the given notation |
| load_bookmark_dataB | Load bookmarks and history data from files |
| organize_and_categorizeB | Clean, deduplicate, and categorize bookmark data |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools have unclear boundaries and overlapping purposes. 'load_bookmark_data' and 'organize_and_categorize' both deal with bookmark data, making it ambiguous which to use for basic operations. 'roll_dice' is completely unrelated to the web search/domain theme, creating confusion about the server's core purpose. An agent would struggle to differentiate when to use each tool appropriately.
The naming conventions are mixed but still readable. 'load_bookmark_data' and 'web_search' follow a verb_noun pattern, while 'organize_and_categorize' uses a verb_and_verb style and 'roll_dice' is a simple verb_noun. There's no consistent pattern across all tools, but the names are descriptive enough to understand their functions individually.
With only 4 tools, the count feels too thin for a 'Tavily Web Search MCP Server' as implied by the name. The inclusion of unrelated tools like 'roll_dice' and bookmark management functions suggests poor scoping. A focused web search server would typically have more search-related operations, making this set appear incomplete and mismatched to its stated purpose.
There are significant gaps in the tool surface for a web search domain. While 'web_search' exists, there's no support for advanced search features, result filtering, or search history management. The bookmark tools are incomplete without create/update/delete operations, and 'roll_dice' is entirely out of scope. This creates dead ends for agents trying to perform comprehensive web search tasks.