Skip to main content
Glama
A1-x-Tech

mcp-google-custom-search

Image search

search_images
Read-onlyIdempotent

Search for images using Google Programmable Search Engine with filters like size, type, color, license, language, country, date, and site. Returns direct image URLs, dimensions, and thumbnails.

Instructions

Image search through your Google Programmable Search Engine (searchType=image). Works only when the engine has "Image search" enabled in its control panel — otherwise the API answers 400. Each item's url is the image file itself; image.context_url is the page hosting it, with width/height/byte_size and a thumbnail_url (plus its dimensions) for previews. Everything else matches the search tool: same filters (language/country, safe search, site include/exclude, date_restrict, file_type, rights — use rights for reusable images), same pagination (max 10 per call, 100 per query, paginate via next_start), same quota (one unit per call). Image-only filters: size (icon..huge), type (clipart/face/lineart/stock/photo/animated), color_type (mono/gray/color/trans) and dominant_color.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNoResults per page, 1..10 (API maximum 10; default 10).
safeNoSafe search: active filters adult content, off (the API default) does not.
sizeNoImage size class, from icon to huge.
sortNoSort expression, e.g. "date" for newest-first. Omit for relevance (usually better).
typeNoKind of image.
queryYesThe search query, Google syntax included (quotes, site:, filetype:, OR, -exclusions).
startNo1-based index of the first result — use next_start/previous_start from the previous page. The API serves at most 100 results per query, so start + num - 1 must stay <= 100 (enforced: a wider window is rejected without spending quota).
rightsNoLicense filter: cc_publicdomain, cc_attribute, cc_sharealike, cc_noncommercial, cc_nonderived (combine with |).
countryNoGeolocation bias — rank results as if searching from this country, e.g. "de". Soft signal.
languageNoOnly results in this language, e.g. "en", "de", "zh-CN".
or_termsNoSpace-separated words — each result must contain at least one of them.
engine_idNoProgrammable Search Engine id (cx) to search with, overriding the configured GOOGLE_CUSTOM_SEARCH_ENGINE_ID. Omit to use the configured engine.
file_typeNoOnly files of this type, e.g. "pdf", "xlsx", "svg".
color_typeNomono = black & white, trans = transparent background.
exact_termsNoA phrase every result must contain.
site_searchNoA site or domain to include or exclude, e.g. "example.com" — pair with site_search_filter.
date_restrictNoOnly results from the last N days/weeks/months/years: "d7", "w2", "m6", "y1", ...
exclude_termsNoA word or phrase no result may contain.
dominant_colorNoPrefer images dominated by this color.
include_pagemapNoAttach each result's raw pagemap (OpenGraph/metatags/thumbnails and other structured page data). Verbose — leave off unless you need page metadata.
country_restrictNoHard filter — only documents Google attributes to this country, e.g. "DE".
filter_duplicatesNoGoogle's duplicate-content filter (default on). false returns near-duplicate results too.
interface_languageNoInterface language used to interpret the query, e.g. "de". Improves non-English relevance.
site_search_filterNoinclude = only results from site_search, exclude = everything but it. Default include.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/idempotent annotations, the description reveals important behavior: the 400 error condition, the meaning of item.url vs image.context_url, thumbnail and size fields, quota cost, pagination behavior via next_start, and the full set of image-only filters. This is rich, non-obvious behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence earns its place. It front-loads the core purpose and the critical engine prerequisite, then covers result shape, shared behavior, and image-only filters in a logical progression. It efficiently leverages the sibling search tool instead of repeating all shared details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 24 parameters, no output schema, and meaningful API quirks, the description is remarkably complete. It covers prerequisites, error conditions, result semantics, pagination, quotas, shared filters, and image-specific filters, leaving little ambiguity for an agent needing to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters well. The description still adds value by grouping filters, clarifying shared semantics with the search tool, emphasizing 'use rights for reusable images', and explaining pagination/quota behavior that the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific operation: image search through a Google Programmable Search Engine with searchType=image. It clearly distinguishes this from the sibling 'search' tool by focusing on image-specific behavior and explicitly saying 'Everything else matches the search tool.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: use this for image search, and it requires the engine to have Image search enabled, otherwise the API returns 400. It references the alternate generic search tool for shared filters/pagination behavior, though it does not explicitly state 'use search for non-image queries'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/A1-x-Tech/mcp-google-custom-search'

If you have feedback or need assistance with the MCP directory API, please join our Discord server