Google PSE MCP Server
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 |
|---|---|
| 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 clearly defined as web search, making it perfectly distinct.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'search' is straightforward and follows a simple verb pattern.
A single tool for a Google search server is too minimal for typical agent workflows. While it covers the core function, it lacks related operations like filtering results, handling pagination, or accessing other Google services, making it feel thin and limiting.
The tool set is severely incomplete for a Google search domain. It only provides basic search functionality, missing essential features such as advanced search parameters, result parsing, or integration with other Google APIs (e.g., Maps, Translate), which would be expected in a more comprehensive server.