Skip to main content
Glama
Sign In

scrapeunblocker-mcp-remote

by com.scrapeunblocker
OverviewDiscussionsAdmin

Scrape Google Images results

google_images
Read-only

Runs the Google Images vertical (udm=2) for q and returns the image results as JSON. Every result carries imageUrl (the full-resolution origin image, not a Google thumbnail; for an image found inside a document such as a PDF, which has no URL of its own, it is Google's thumbnail and sourcePageUrl is the document), sourceDomain and googleImagesUrl (the Google Images viewer link, i.e. the /imgres?... URL a browser copies from the result tile), plus sourcePageUrl, title, sourceName, thumbnailUrl, width, height and fileSize where available. Set proxy_country to target a market: the Google market (gl) follows it automatically, and gl is only an optional override. pages fetches up to 5 result pages of ~100 each; every page fetched is billed as one request. time_range (past hour/day/week/month/year) or date_from/date_to limit the results to images Google found in that period, so a repeated scan returns only what is new. Returns JSON. Billed like an API request; listing plugins bill one unit per result page they fetch, so keep max_results modest.

Input Schema

NameRequiredDescriptionDefault
qYesImage search term, e.g. 'eiffel tower'.
glNoOptional Google market override (ISO-2, e.g. 'us', 'de'). Leave empty and the market follows `proxy_country` ('us' when neither is set). The market, not the proxy country, is what decides which images rank.
pagesNoHow many Google Images result pages to fetch (1-5, ~100 results each; Google stops at ~400-500 per query). Each page fetched is billed as one request. Default: 1.
date_toNoOnly images Google found on or before this date (YYYY-MM-DD). Works alone or with `date_from`; cannot be combined with `time_range`.
date_fromNoOnly images Google found on or after this date (YYYY-MM-DD). Works alone or with `date_to`; cannot be combined with `time_range`.
time_rangeNoOnly images Google found within this recent period: `hour`, `day`, `week`, `month` or `year` (Google Images' Tools > Time filter). Use it to get just the new results on repeated scans. Cannot be combined with `date_from`/`date_to`.
max_resultsNoOptional cap on the number of results returned (default: all results of the fetched pages).
proxy_countryNoProxy country the request is sent from (ISO-2, e.g. 'US', 'DE'). Image results are market-specific.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / max_results / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / max_results / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / pages / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / pages / minimum
      Added value: +-9007199254740991
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/open-world/no-destructive, yet the description adds substantial behavior: billing is per fetched page, Google saturates around 400-500 results per query, and every page fetched costs a request. It also discloses a non-obvious edge case (PDF-embedded images return Google's thumbnail as `imageUrl` with `sourcePageUrl` pointing at the document).

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

Conciseness4/5

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

The purpose and scope are front-loaded in the first sentence, and the billing/pagination guidance is appended logically at the end. The long result-field sentence is dense with parentheticals and harder to scan, but nearly every clause carries actionable information rather than filler.

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?

With no output schema, the description takes on the burden of explaining return values and does so field by field, including the thumbnail-vs-original distinction. Combined with billing and market behavior, an agent has everything needed to call this tool correctly and predict cost.

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 baseline is 3, but the description adds real meaning: it explains that `proxy_country` implicitly sets the Google market (`gl`) and that `gl` decides ranking while being only an optional override. It also characterizes `pages` as ~100 each, capped at 5, and billed per page.

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 opening sentence names a specific verb ('Runs'), the exact resource (the Google Images vertical, `udm=2`) and the output form (image results as JSON). This clearly separates it from sibling tools like `google_search` and `google_shopping` without needing to inspect the schema.

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?

It gives concrete usage context: `time_range`/date filters for 'repeated scans' returning only new images, and `proxy_country` for market targeting. It also flags the mutual exclusion of `time_range` with date filters. It stops short of explicitly naming a sibling alternative ('use google_search for web pages'), so it is clear but not fully directive.

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

All scrapeunblocker-mcp-remote toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources