Skip to main content
Glama

rowfeed/google-images-api

rowfeed--google-images-api
Destructive

This tool calls the Actor "rowfeed/google-images-api" and retrieves its output results. Actor description: Google Images API and image scraper: every image Google Images shows for a search, with the full-size image URL, thumbnail, title, the page it is on and its website. Up to 700 images per search, any country and language. $2 per 1,000 images.

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the results (English name). Example values: "English"English
locationNoCountry (or city) the search is made from, e.g. United States, Germany, London,England,United Kingdom. Example values: "United States"United States
searchesNoWhat you would type into Google Images. Up to 500. An image found by several searches is returned (and charged) once. Example values: ["modern kitchen design"]
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
maxImagesNo1 to 700. Example values: 20

Output Schema

NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "alt_text": {
      +      "type": "string"
      +    },
      +    "checked_at": {
      +      "type": "string"
      +    },
      +    "domain": {
      +      "type": "string"
      +    },
      +    "from_snapshot": {
      +      "type": "boolean"
      +    },
      +    "image_url": {
      +      "type": "string"
      +    },
      +    "page_url": {
      +      "type": "string"
      +    },
      +    "position": {
      +      "type": "number"
      +    },
      +    "query": {
      +      "type": "string"
      +    },
      +    "related_searches": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "thumbnail_url": {
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "type": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / language / prefill
      Added value: +"English"
    • addedInput schema / properties / location / prefill
      Added value: +"United States"
    • addedInput schema / properties / searches / prefill
      Added value: +[
      +  "modern kitchen design"
      +]
  3. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"Live lookups need a paid Apify plan (any plan). The pre-filled example works on the free plan."
  4. Changed1 schema field changed
    • removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Removed value: -{
      -  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      -  "properties": {
      -    "alt_text": {
      -      "type": "string"
      -    },
      -    "checked_at": {
      -      "type": "string"
      -    },
      -    "domain": {
      -      "type": "string"
      -    },
      -    "from_snapshot": {
      -      "type": "boolean"
      -    },
      -    "image_url": {
      -      "type": "string"
      -    },
      -    "page_url": {
      -      "type": "string"
      -    },
      -    "position": {
      -      "type": "number"
      -    },
      -    "query": {
      -      "type": "string"
      -    },
      -    "related_searches": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "source": {
      -      "type": "string"
      -    },
      -    "thumbnail_url": {
      -      "type": "string"
      -    },
      -    "title": {
      -      "type": "string"
      -    },
      -    "type": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
  5. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "alt_text": {
      +      "type": "string"
      +    },
      +    "checked_at": {
      +      "type": "string"
      +    },
      +    "domain": {
      +      "type": "string"
      +    },
      +    "from_snapshot": {
      +      "type": "boolean"
      +    },
      +    "image_url": {
      +      "type": "string"
      +    },
      +    "page_url": {
      +      "type": "string"
      +    },
      +    "position": {
      +      "type": "number"
      +    },
      +    "query": {
      +      "type": "string"
      +    },
      +    "related_searches": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "thumbnail_url": {
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "type": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  6. Changed1 schema field changed
    • removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Removed value: -{
      -  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      -  "properties": {
      -    "alt_text": {
      -      "type": "string"
      -    },
      -    "checked_at": {
      -      "type": "string"
      -    },
      -    "domain": {
      -      "type": "string"
      -    },
      -    "from_snapshot": {
      -      "type": "boolean"
      -    },
      -    "image_url": {
      -      "type": "string"
      -    },
      -    "page_url": {
      -      "type": "string"
      -    },
      -    "position": {
      -      "type": "number"
      -    },
      -    "query": {
      -      "type": "string"
      -    },
      -    "related_searches": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "source": {
      -      "type": "string"
      -    },
      -    "thumbnail_url": {
      -      "type": "string"
      -    },
      -    "title": {
      -      "type": "string"
      -    },
      -    "type": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
  7. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "alt_text": {
      +      "type": "string"
      +    },
      +    "checked_at": {
      +      "type": "string"
      +    },
      +    "domain": {
      +      "type": "string"
      +    },
      +    "from_snapshot": {
      +      "type": "boolean"
      +    },
      +    "image_url": {
      +      "type": "string"
      +    },
      +    "page_url": {
      +      "type": "string"
      +    },
      +    "position": {
      +      "type": "number"
      +    },
      +    "query": {
      +      "type": "string"
      +    },
      +    "related_searches": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "thumbnail_url": {
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "type": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  8. Changed1 schema field changed
    • removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Removed value: -{
      -  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      -  "properties": {
      -    "alt_text": {
      -      "type": "string"
      -    },
      -    "checked_at": {
      -      "type": "string"
      -    },
      -    "domain": {
      -      "type": "string"
      -    },
      -    "from_snapshot": {
      -      "type": "boolean"
      -    },
      -    "image_url": {
      -      "type": "string"
      -    },
      -    "page_url": {
      -      "type": "string"
      -    },
      -    "position": {
      -      "type": "number"
      -    },
      -    "query": {
      -      "type": "string"
      -    },
      -    "related_searches": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "source": {
      -      "type": "string"
      -    },
      -    "thumbnail_url": {
      -      "type": "string"
      -    },
      -    "title": {
      -      "type": "string"
      -    },
      -    "type": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
  9. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "alt_text": {
      +      "type": "string"
      +    },
      +    "checked_at": {
      +      "type": "string"
      +    },
      +    "domain": {
      +      "type": "string"
      +    },
      +    "from_snapshot": {
      +      "type": "boolean"
      +    },
      +    "image_url": {
      +      "type": "string"
      +    },
      +    "page_url": {
      +      "type": "string"
      +    },
      +    "position": {
      +      "type": "number"
      +    },
      +    "query": {
      +      "type": "string"
      +    },
      +    "related_searches": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "thumbnail_url": {
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "type": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  10. Changed1 schema field changed
    • removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Removed value: -{
      -  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      -  "properties": {
      -    "alt_text": {
      -      "type": "string"
      -    },
      -    "checked_at": {
      -      "type": "string"
      -    },
      -    "domain": {
      -      "type": "string"
      -    },
      -    "from_snapshot": {
      -      "type": "boolean"
      -    },
      -    "image_url": {
      -      "type": "string"
      -    },
      -    "page_url": {
      -      "type": "string"
      -    },
      -    "position": {
      -      "type": "number"
      -    },
      -    "query": {
      -      "type": "string"
      -    },
      -    "related_searches": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "source": {
      -      "type": "string"
      -    },
      -    "thumbnail_url": {
      -      "type": "string"
      -    },
      -    "title": {
      -      "type": "string"
      -    },
      -    "type": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
  11. Added

TDQS

A3.5/5.0
Behavior3/5

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

The description adds real context beyond annotations: per-image pricing, the up-to-700-images ceiling per search, and the shape of the returned records. But annotations declare destructiveHint=true and readOnlyHint=false, and the description frames the tool as merely 'retrieves output results' without saying that invoking it starts a billable Actor run that consumes paid plan credits (that plan caveat sits in the schema, not here). The lifecycle detail lives in the waitSecs schema text rather than the description.

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?

Two sentences with no filler, and the operative content (what is returned and at what cost) is front-loaded. The opening 'This tool calls the Actor ... and retrieves its output results' is slightly boilerplate MCP-wrapper phrasing but still earns its place by identifying the execution model.

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

Completeness4/5

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

With a full input schema, an output schema, and annotations present, the description covers purpose, payload fields, volume ceiling, and cost, which is enough for correct invocation. The main omissions are the paid-plan prerequisite (present only in the schema description) and any polling/long-run behavior, which an agent would otherwise only discover after a capped waitSecs response.

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

Parameters3/5

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

Schema description coverage is 100% and waitSecs, searches, language, location and maxImages are all documented in-schema, so the schema carries the burden. The description corroborates scope ('up to 700 images per search, any country and language') but adds no new syntax or format meaning beyond that, which is the baseline-3 case.

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

Purpose4/5

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

The description names a specific verb (calls the Actor and retrieves its output) and a specific resource (Google Images results for a search), and the Actor blurb enumerates the returned fields (full-size URL, thumbnail, title, source page, website). It does not, however, distinguish this from closely related siblings such as rowfeed--google-serp-api or rowfeed--google-shopping-prices, so an agent must infer the split from the name and payload description alone.

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

Usage Guidelines3/5

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

Usage is only implied: 'every image Google Images shows for a search' tells the agent this is the image-retrieval option, and the '$2 per 1,000 images' line gives a cost signal. There is no explicit when-to-use/when-not statement and no named alternative (e.g., use google-serp-api for web results instead of images), so the agent gets context but no routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.