MCP Gemini Google Search
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_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 has a single, clear purpose that cannot be confused with any other tool in the set.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'google_search' follows a clear and descriptive verb_noun pattern.
A single tool for a search server is too minimal for typical agent workflows, as it lacks complementary tools like filtering, pagination, or advanced search options. This forces agents to rely solely on basic queries without refinement capabilities.
The tool surface is severely incomplete for a search domain, missing essential operations such as filtering results by date, site, or language, handling pagination, or providing search suggestions. This will limit agents to basic, one-off queries without follow-up capabilities.