Google Web Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_KEY | Yes | Your Google API key for Custom Search API | |
| CUSTOM_SEARCH_ENGINE_ID | Yes | Your Custom Search Engine ID |
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_web_searchD | – |
| google_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 2 tools
The two tools, google_web_search and google_search, appear to perform the same action and have no descriptions to distinguish them. An agent cannot reliably tell when to use one over the other.
Both names use snake_case with a google_ prefix, following a consistent convention. The only minor deviation is the extra 'web' token in one name, which does not break the pattern.
Two tools is borderline thin for a search server, and they are redundant rather than complementary. A single clear search tool would likely suffice for the stated purpose.
The surface lacks any description or differentiation between the two search tools. There are no obvious complementary operations such as image search, news search, pagination, or filters to cover a broader search domain.