Google Images MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | HasData API key, created free at https://app.hasdata.com |
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 |
|---|---|
| hasdata_google_images_images_getImageSearchResultsA | Get Image Search Results Scrapes Google Images for a query with advanced filters (size, color, image type, safesearch, domain/country/language, device type) plus page-based pagination (ijn). Returns each image with title, source page URL, direct image URL, thumbnail, dimensions, source domain, and position. Use for visual-asset discovery, reverse-image workflows, dataset collection for ML/CV training, brand/logo monitoring, stock-image sourcing, and grounding multimodal LLMs with fresh image context. |
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 a single tool, there is no possibility of confusing it with another operation. The purpose is clearly stated as image search.
The sole tool name mixes snake_case and camelCase ('hasdata_google_images_images_getImageSearchResults'), making it long and stylistically inconsistent. Although there is no naming pattern to compare against, the internal inconsistency warrants a low score.
A single tool is too few for a server claiming to cover Google Images, especially given the advanced filtering and pagination options that could logically be split into separate concerns (e.g., image search, metadata retrieval). It falls outside the typical 3-15 well-scoped range.
The tool thoroughly covers image search with common filters, pagination, and detailed result data, leaving no critical dead-end for a search-only workflow. However, a broader Google Images server could reasonably include direct image resolution or image metadata endpoints, so it's not a perfect 5.