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 |
| send_gmailC | Send an email using Gmail API. Requires GMAIL_USER and GMAIL_APP_PASSWORD environment variables. |
| read_clipboardA | Read and return the current clipboard text (macOS). Uses |
| write_clipboardA | Write the given text to the clipboard (macOS). Uses |
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 5 tools
The tools have wildly different and unrelated purposes—clipboard operations, dice rolling, email sending, and web searching—with no clear thematic connection, making the set highly ambiguous as a cohesive toolset. An agent would struggle to understand why these specific tools are grouped together, leading to potential misselection based on domain assumptions.
The naming follows a consistent verb_noun pattern (e.g., read_clipboard, roll_dice, send_gmail, web_search, write_clipboard), which is predictable and readable. There are minor deviations like 'web_search' using a noun_verb structure instead, but overall the consistency is strong.
With only 5 tools, the count is reasonable in isolation, but it is inappropriate for the server's stated purpose as 'Tavily Web Search MCP Server'—only one tool (web_search) directly relates to web searching, while the others are unrelated utilities, creating a mismatch in scope.
For a web search server, there are significant gaps in coverage, such as missing tools for advanced search features, result filtering, or API configuration. The inclusion of unrelated tools like clipboard and email operations further dilutes the domain focus, making the surface incomplete for the stated purpose.