Skip to main content
Glama

Search free-to-use images (coming soon)

search_free_images
Read-only

Find legally reusable images from Wikimedia Commons by license, size, orientation, and format, with attribution details and filters to ensure commercial use rights.

Instructions

COMING SOON: this Kanto Labs actor is not public on the Apify Store yet. Until it is, calls return an 'actor not yet public' error and nothing is charged. Find pictures you may legally reuse: searches the 100M+ freely licensed files on Wikimedia Commons through the official MediaWiki API and returns only images under free licenses that allow commercial use (public domain, CC0, CC BY, CC BY-SA...). Each image comes with the full-size original URL, a thumbnail URL, the file page, width, height, orientation, license, license family, whether attribution or share-alike is required, the author, a ready-to-paste attribution line (text and HTML), community quality marks and any extra restrictions (trademarks, personality rights). Filter by license ("noAttribution" = public domain/CC0 only, "commercialNoShareAlike" = PD/CC0/CC BY), minimum size, orientation and file type. Use it for article featured images, product or slide visuals, maps, flags, diagrams, historical photos and licensed image datasets. Works best for concrete subjects (animals, food, places, objects, events); abstract stock concepts return fewer matches, so search for the concrete scene. Not legal advice: follow each image's license. Cost: $0.001 per image returned, billed to your Apify account; filters apply before charging and a search with no match is free. Runs the Apify actor kantolabs/free-image-search with your APIFY_TOKEN; maxTotalChargeUsd caps the spend per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
licenseNo"any" (default): every free license. "commercialNoShareAlike": public domain, CC0 and CC BY only. "noAttribution": public domain and CC0 only (no credit needed).
queriesYesSearch terms, one per item, e.g. ["golden retriever puppy", "tokyo skyline night"]. English works best.
languageNoPreferred language for titles and descriptions, e.g. en (default), de, fr, ja.
minWidthNoMinimum width in px. Default 0 (any).
fileTypesNoFormats to include. Default ["jpg", "png", "webp"]; use ["svg"] for maps, flags, icons and diagrams.
minHeightNoMinimum height in px. Default 0 (any).
orientationNoDefault any.
timeoutSecsNoGive up after this many seconds (max 300, Apify's limit for synchronous runs). Default 280. For big batches, split the input into several calls.
thumbnailWidthNoWidth of thumbnailUrl in px. Default 800. imageUrl is always the full original.
excludeRestrictedNoSkip files with trademark, personality-rights or insignia restrictions (recommended for ads). Default false.
maxTotalChargeUsdNoHard spending cap for this call in USD, enforced by Apify: the run stops once it has charged this much. Default 1 (server setting KANTO_MAX_CHARGE_USD).
maxResultsPerQueryNoImages per search after filters. Default 20. Each is charged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/destructiveHint annotations, the description discloses critical behaviors: the current 'coming soon' error state, '$0.001 per image returned' with filters applied before charging, no charge on no-match searches, execution as 'the Apify actor kantolabs/free-image-search with your APIFY_TOKEN', and the maxTotalChargeUsd spending cap. This is rich context that annotations do not provide.

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 description is long but well-organized and front-loaded: the 'COMING SOON' warning leads, followed by purpose, output details, filters, use cases, caveats, legal note, and cost. Each sentence contributes value, though a few license-related details repeat information already in the schema.

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 12 parameters and no output schema, the description fully compensates by enumerating all returned fields (full-size URL, thumbnail, file page, dimensions, license family, attribution requirements, author, attribution line, quality marks, restrictions), plus cost, error behavior, filters, and legal advice. Nothing an agent needs to call or interpret the result is missing.

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%, so the baseline is 3. The description adds slight interpretive value by explaining license tiers ('noAttribution' = PD/CC0 only, 'commercialNoShareAlike' = PD/CC0/CC BY) and file-type use cases, but most of that is also present in the schema descriptions. No substantial new parameter meaning is added.

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?

Description uses a specific verb+resource: 'searches the 100M+ freely licensed files on Wikimedia Commons through the official MediaWiki API' and states the exact deliverable (images under free licenses with legal reuse details). This clearly distinguishes it from sibling download_images and other unrelated tools.

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 use cases ('article featured images, product or slide visuals, maps, flags, diagrams, historical photos') and a practical caveat ('abstract stock concepts return fewer matches, so search for the concrete scene'). It does not explicitly name alternative tools or exclusion conditions, so it falls short of a 5.

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