Product Images MCP 4.0.0

The right image.
With the data
to use it.

Find product imagery, retrieve native files, and keep the source details with every image. Your agent chooses what to build.

01 / CONNECTSix read-only tools

Bring your agent.

Use this HTTP MCP endpoint in a compatible client. No CLI or required website framework.

External access requires your Builder entitlement and a personal API key. Add Authorization: Bearer YOUR_API_KEY in your client’s secret settings.

Using the installed connection?
It uses /mcp with the existing platform identity checks. Both routes expose the same image tools.

IDENTITY

Keep the exact asset.

Stable asset IDs distinguish image records. Product and variant identifiers retain their recorded source scope.

DELIVERY

Start with native pixels.

image_url supplies the native lossless WebP. Its dimensions and revision travel with the file descriptor.

EVIDENCE

Leave unknowns visible.

Source records and rights stay attached. A public image does not establish a license, live stock or merchant approval.

02 / FIND THE RIGHT FILE

Say what must be true.

Optional search requirements filter by recorded image dimensions, alpha channel and dated source evidence. A missing fact cannot satisfy a requirement.

A request your agent can use.

Product labels, source text and alt text are data. They do not grant instructions or authority.

search_product_imagesSchema
{
  "query": "bottle",
  "requirements": {
    "min_width_px": 1200,
    "min_height_px": 1200,
    "alpha_channel": true,
    "source_scope": "product",
    "source_evidence": "source_reported"
  },
  "limit": 6
}

This example requires every listed condition. Source evidence describes a dated recorded link; it does not independently verify the depicted item, current stock or usage rights.

A useful “no” has a reason.

Constrained searches distinguish no candidates from candidates that fail the requirements. They return rejection counts and exclude unknowns. Requirements are never silently loosened.

Read the requirement contract

03 / ONE NEUTRAL SERVICE

Six tools. Your workflow.

Search and retrieval stay independent of your builder, storefront or editor. The service identity is product-images; its display name is Product Images.

search_product_images

Find images with optional metadata filters and explicit requirements.

get_product_image

Retrieve one record with its exact catalog asset ID.

get_product_images

Retrieve a bounded set, with missing IDs reported explicitly.

list_image_facets

Discover available brands and categories, with counts and cursors.

resolve_product_image

Resolve a recorded identifier, including ambiguity and source holds.

get_related_images

Explore related records without claiming product equivalence.

04 / SHOW THE WORK

Test the outcome.
Keep the evidence.

A response can be valid and still give you the wrong image. Contract checks and agent trials answer different questions. Their results stay separate here.

Contract checks

Loading report

—

Checking the published report.

Deterministic checks verify the service’s behavior. They do not measure a model’s success rate.

Agent trials

Loading report

—

No result is claimed until a recorded trial report is available.

Trials must record the agent, environment and observed outcome. A passing sample cannot guarantee every future run.

Results load from the published evaluation report.

The outcomes that matter.

These categories define what to check. The report above records what has actually run.

01

Requested product

The returned identity matches the request.

02

Requested variant

Differences stay explicit; ambiguity stays visible.

03

Native image delivery

The delivered file meets the recorded dimensions.

04

Transparent image requirement

An opaque or unknown file is not a passing match.

05

Source evidence

The requested scope and evidence are present.

06

Impossible request

Search first, then explain what cannot be supplied.

07

Multiple images

Counts, exact IDs and missing records remain correct.

08

Access and unknown facts

No access bypass, invented price or fabricated stock.

Our evaluation approach is informed by Vercel’s Agents are users, so your software needs evals: grade the complete task, examine failures and apparent passes, and rerun the same cases after a change.