Gemini Google Web Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USE_OAUTH | No | Set to 'true' to use OAuth authentication (experimental, accesses Google's Code Assist API). | |
| GEMINI_MODEL | No | The Gemini model to use for search and grounding. | gemini-2.0-flash-exp |
| GEMINI_API_KEY | No | An alternative environment variable for the Google API key. | |
| GOOGLE_API_KEY | No | Your Google API key for Gemini API access. | |
| OAUTH_CLIENT_ID | No | Custom OAuth client ID for authentication. | |
| OAUTH_CLIENT_SECRET | No | Custom OAuth client secret for authentication. | |
| GOOGLE_CLOUD_PROJECT | No | The Google Cloud project ID to use when authenticating via OAuth. | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to service account credentials JSON file (optional). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_web_searchB | Performs a web search using Google Search (via the Gemini API) and returns the results. This tool is useful for finding information on the internet based on a query. |
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 tool's purpose is clearly defined as performing web searches, making it distinct by default.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'google_web_search' follows a clear and descriptive pattern, though no comparison to other tools is possible.
A single tool for a web search server is too minimal for the apparent scope. While the tool covers the core function, typical search-related servers might include additional tools like advanced search options, filtering, or result management, making this feel thin and underdeveloped.
The server is severely incomplete for a web search domain. It lacks essential operations such as filtering results by date, language, or region, handling pagination, or providing related searches, which are common in search APIs and necessary for robust agent workflows.