Google Images Search MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your Google API key | |
| SEARCH_ENGINE_ID | Yes | Your Google 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 |
|---|---|
| search_imageC | Search the image(s) online |
| persist_imageA | Store image at URL to folder relative to current workspace. If targetPath does not exist, the tool will create it automatically. |
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 have clearly distinct purposes: search_image retrieves images online, persist_image saves a specific image from a URL. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb_noun pattern (search_image, persist_image) using snake_case, which is predictable and clear.
With only 2 tools, the set is minimal for a search-and-persist workflow. While it covers the core actions, it feels slightly thin compared to typical server scopes of 3-15 tools.
The tools cover the essential workflow: search for images and persist a chosen image. No obvious gaps for the stated purpose, though additional functions like listing persisted images or metadata retrieval could be useful.