searchapi-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARCHAPI_API_KEY | Yes | Your SearchApi.io API key |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_searchB | Search Google via SearchApi. Returns direct-answer features (answer box, knowledge graph, AI overview) when present, followed by organic results with title, link, and snippet. |
| google_shoppingA | Search Google Shopping via SearchApi. Returns products with title, price, seller, rating, and delivery info. |
| google_jobsA | Search Google Jobs via SearchApi. Returns job listings with title, company, location, apply link, and a short description. |
| youtube_searchB | Search YouTube via SearchApi. Returns videos with title, link, channel, views, duration, and publish time. |
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
Each tool targets a clearly distinct search vertical: shopping, jobs, YouTube, and general web. There is no overlap in purpose or output type, so an agent can easily select the right tool for a given query.
All names follow a consistent snake_case pattern of provider/vertical + search (google_shopping, google_jobs, youtube_search, google_search). The convention is predictable and readable across the set.
Four tools is a well-scoped set for a search aggregator, with each tool representing a distinct search category and no redundancy. The count falls comfortably within the typical 3-15 range for a focused server.
The surface covers four popular verticals but lacks common search types such as news, images, maps, or scholarly results that a general SearchApi wrapper would typically offer. This gap may force agents to work around missing capabilities for many real-world tasks.