Google Search MCP
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 |
|---|---|
| searchD | – |
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 ambiguity or overlap between tools. The single tool 'search' has a distinct and clear purpose by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'search' follows a simple, clear verb pattern.
One tool is too few for a server named 'Google Search MCP', which suggests a domain that might benefit from more functionality (e.g., advanced search options, filtering, or result management). A single tool feels thin and under-scoped for such a purpose.
The server is severely incomplete for a search domain. With only a basic 'search' tool and no description, it lacks obvious features like pagination, filtering by date or type, or handling search results, which are essential for effective search operations.