SearchAPI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
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 9 tools
Most tools are clearly distinct by their target resource (flights, hotels, maps, videos), but there is some ambiguity between search_google_flights and search_google_flights_calendar, and between search_google_hotels and search_google_hotels_property, which could cause confusion about when to use each. The get_current_time tool stands out as unrelated to the search domain, creating a minor disjunction.
All tool names follow a consistent snake_case pattern with a clear verb_noun structure, primarily using 'search_google_' as a prefix for most tools. This predictability makes it easy for an agent to understand and navigate the tool set without confusion over naming conventions.
With 9 tools, the count is reasonable for a search-focused API, though it feels slightly heavy due to the inclusion of get_current_time, which doesn't align with the core domain. The search tools are well-scoped, but the outlier tool slightly reduces the appropriateness.
The tool set covers various Google search domains (flights, hotels, maps, videos) but has notable gaps: there is no general web search tool (search_google is present but ambiguous without a description), and coverage is inconsistent (e.g., flights and hotels have multiple tools, while videos has only one). This may lead to agent failures for common search queries outside the specified categories.