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 (~176.93 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.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses pagination and metered billing, but does not explain permissions, side effects, rate limits, dependencies such as historyPrices requiring marketPrices, or return behavior.

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, front-loaded with the core purpose and followed by billing. There is no wasted text.

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 description covers the basic operation and billing context, but with five optional parameters and no output schema it does not explain return values or when the price-related options should be used. It is adequate but leaves notable gaps for an agent.

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 all five parameters are already documented in the schema. The description adds only the pagination and billing summary, not additional meaning for page, size, or the price-related parameters.

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: it "Lists products" and adds the pagination scope. That is clear enough to identify the operation, but it does not distinguish this from sibling tools like get_api_external_search or get_api_external_product_of_market.

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?

It says what the tool does but gives no guidance on when to use it instead of sibling tools such as search, last, or product_of_market. There are no prerequisites, exclusions, or alternative-selection cues.

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