Skip to main content
Glama
Procurement MCP

Procurement MCP

by belikh

search_by_image

Find supplier listings that match a product photo, returning price, minimum order, and supplier name across wholesale, B2B, or retail marketplaces.

Instructions

Find supplier listings that match a product photo.

Give it a photo, for example from a Gumtree or Facebook listing, and it returns matching listings with price, minimum order and supplier name. Runs a hosted Apify actor that costs about $0.10 per search.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image_url": "<image_url>"
    },
    "name": "search_by_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_urlYesPublic URL of a product photo to reverse-search (JPG/PNG)
destinationNoWhere to search: 1688 = wholesale factories, alibaba = B2B, aliexpress = retail, global = Amazon, Walmart, eBay and other retail sites1688
max_resultsNoCap on matches returned

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does meaningful work: it names the backing dependency (a hosted Apify actor) and quantifies cost at about $0.10 per search, which is exactly the kind of thing an agent needs before invoking. It omits failure modes, latency, and authentication expectations, keeping it out of 5 territory.

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?

Three short sentences, front-loaded with the purpose, then the invocation cue, then cost. Nothing is repeated from the schema and no sentence is wasted.

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?

An output schema exists, so the description need not document return values (it briefly does anyway). Purpose, input cue, cost, and external dependency are all covered; only operational details like latency or error behavior are absent, which is minor for a three-parameter read tool.

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%, including an enum breakdown for destination and bounds for max_results, so the schema already does the heavy lifting. The description only gestures at 'a photo' and does not add meaning for destination or max_results, so the baseline of 3 applies.

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 gives a specific verb and resource: 'Find supplier listings that match a product photo.' This is clearly a reverse-image search rather than the text-based offer search implied by the sibling search_offers, though the description never explicitly contrasts itself with that sibling.

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?

'Give it a photo, for example from a Gumtree or Facebook listing' establishes the concrete situation in which to reach for this tool. There is no explicit when-not guidance and no alternative tool named for text-based searching, 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.