Google Search 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
| Name | Description |
|---|---|
| google_searchA | Performs Google searches using the official API with automatic API key rotation. Features:
Parameters:
Returns a JSON list of results with title, link, description and domain. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as performing Google searches, leaving no ambiguity for an agent to misselect among alternatives.
The single tool name 'google_search' follows a clear and consistent verb_noun pattern. Since there are no other tools to compare against, the naming is inherently consistent and predictable within this server's scope.
A single tool is too few for a server named 'Google Search MCP Server', as it suggests a broader scope that might include related operations like image search, news search, or search history management. The tool count feels thin and limited for the apparent domain.
The server is severely incomplete for a Google Search domain, as it only provides basic web search functionality. Obvious gaps include missing tools for image search, news search, video search, search suggestions, or advanced filtering, which are typical in such APIs and would be needed for comprehensive agent workflows.