Skip to main content
Glama

product-barcode-api

by com.jojapi
OverviewDiscussionsAdmin

Fetch Product

get_api_external_getProducts

Lists products using pagination. Billing per call: Credits: metered (~260.61 avg).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 0)0
sizeNoPage size (default: 10, maximum: 100). It returns a number of products equal to the page size and consumes credits based on the number of products returned.20
marketPricesNoThis setting controls whether 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 consumed for every 10 market price data points.false
historyPricesNoAdds 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
preferredMarketsNoIt allows the user to specify the preferred markets for which they wish to view product prices. When this parameter is provided, price information is returned only for the listed markets within the `markets` field. If the parameter is not provided, price information for all markets is displayed. Users can specify multiple markets by separating them with commas (e.g., `preferredMarkets=A101,Migros`). If data is available, 1 credit is consumed for every 10 market-price data points.A101,Migros

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / marketPrices / description
      Previous value: -"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."New value: +"This setting controls whether 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 consumed for every 10 market price data points."
    • changedInput schema / properties / preferredMarkets / description
      Previous value: -"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."New value: +"It allows the user to specify the preferred markets for which they wish to view product prices. When this parameter is provided, price information is returned only for the listed markets within the `markets` field. If the parameter is not provided, price information for all markets is displayed. Users can specify multiple markets by separating them with commas (e.g., `preferredMarkets=A101,Migros`). If data is available, 1 credit is consumed for every 10 market-price data points."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It does disclose a genuinely useful behavioral trait absent from structured data: metered billing with an average credit cost. Beyond that, it says nothing about return format, rate limits, or pagination termination behavior, and 'Lists' only implicitly signals a read-only operation.

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?

Two short sentences with the purpose stated first and billing second. Nothing is padded or redundant; every sentence earns its place.

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?

For a paginated list tool with a fully documented schema and no output schema, the description covers purpose and cost but omits any routing guidance against its many siblings. Given the crowded sibling set, that omission leaves a real gap in what the agent needs to select this tool correctly.

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 the parameter descriptions are rich (credit costs, defaults, market filtering, dependencies like historyPrices requiring marketPrices). The description adds nothing beyond the schema on parameters, 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 states a specific verb and resource ('Lists products') and mentions pagination as the mechanism. However, it does not differentiate this tool from close siblings such as get_api_external_search or get_api_external_product_of_market, leaving the agent to guess why it would list products here rather than search for them.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the seven sibling tools. Nothing indicates whether this is a bulk catalog listing versus a targeted lookup, nor are there any prerequisites or exclusions mentioned. 'Using pagination' is a mechanism, not a usage guideline.

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 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources