product-barcode-api

Product Search

get_api_external_search

Searches for products by barcode or name; returns a minimum of 1 and a maximum of 10 products. Billing per call: Credits: metered (~3.9 avg).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	It allows the user to specify the name or barcode of the product they wish to search for. Using this parameter, the system searches for products based on name or barcode matches and returns the results.	Çikolatalı Gofret
`marketPrices`	No	It controls whether or not price information for the requested products at stores is retrieved. If set to `true`, the product's store prices are also returned; if set to `false` or left unspecified, only the product's basic information is retrieved. If data is available, +1 credit is spent for each market-price data point.	false
`historyPrices`	No	Adds historical price information for the requested product from available markets to the response. The `marketPrices` parameter must be set to `true`. If historical price information is available, 1 credit is consumed.	false
`preferredMarkets`	No	It allows the user to specify the preferred markets for which they wish to see product prices. If this parameter is provided, price information is returned in the `markets` field only for the markets listed. If the parameter is not provided, price information for all markets is displayed. If the user wishes to specify multiple markets, they can submit them separated by commas (e.g., `preferredMarkets=A101,Migros`). If data is available, +1 credit is consumed for each market-price data point.	A101,Migros

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It does disclose operational details: a minimum/maximum result count and metered billing of roughly 3.9 credits per call. However, it does not explain how the optional parameters can affect credits, response content, or what happens when no product matches.

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?

The description is only two sentences, front-loads the core search action, and includes the most important operational constraint and billing note. Every sentence earns its place with no redundant filler.

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

Completeness3/5

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

The input schema covers parameter semantics well, but there is no output schema and no annotations. The description does not explain the expected response structure, the relationship between parameters and credits beyond the average, or when to choose this tool over similar siblings, leaving an agent to make inferences.

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 schema already documents all four parameters and their behavior, including marketPrices, historyPrices, and preferredMarkets. The tool description adds no parameter-specific meaning beyond stating that search can be by barcode or name, which is already present in the schema.

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 clearly identifies a specific verb and resource: it searches for products by barcode or name, and states the result count range (1 to 10). It does not explicitly distinguish this tool from siblings like get_api_external_getProducts, so it is clear but not fully differentiated.

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?

The description implies when to use the tool: when searching for a product by barcode or name. However, it gives no explicit guidance about when to prefer this tool over sibling tools, nor any exclusions or alternatives.

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

All product-barcode-api tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0

Disambiguation4/5

Each tool generally targets a distinct concern: paginated product listing, recent products, barcode/name search, current store price, price history, market list, and DB credentials. Some overlap exists between listing and search tools, but the descriptions are clear enough to prevent serious misselection.

Naming Consistency2/5

All tools share the get_api_external_ prefix, but the remainder is inconsistent: getProducts and marketList use camelCase, product_of_market and get_db_info use snake_case, while history and last are bare nouns without a clear verb. The naming style feels mixed rather than following a predictable pattern.

Tool Count5/5

Seven tools is a reasonable, well-scoped size for a barcode/product lookup API. Each tool covers a meaningful part of browsing products, searching, retrieving prices, and accessing historical data without unnecessary bloat.

Completeness4/5

The API covers core read-only workflows: search, paginated product lists, current product pricing by market, price history, recent updates, and available markets. A minor gap is the lack of a dedicated exact-barcode product lookup separate from search, but existing tools can handle common use cases.

Resources

Need Help?