MCP Google Custom Search Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_KEY | Yes | Your Google Custom Search API key | |
| GOOGLE_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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchC | Search the web using Google Custom Search API |
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 singular and clearly defined, eliminating any ambiguity in tool selection.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'search' is straightforward and follows a simple verb pattern appropriate for its function.
A single tool is too few for a server with a purpose like web search, which could benefit from additional tools such as filtering, pagination, or advanced search options. This minimal set feels thin and limits functionality.
The tool surface is severely incomplete for a web search domain. While the basic search function is covered, there are obvious gaps such as no tools for result refinement, handling multiple pages, or accessing search metadata, which could lead to agent failures in complex tasks.