Skip to main content
Glama

mcp-livedatapro

by site.livedatapro
OverviewDiscussionsAdmin

getEcommercePricing

Live Amazon, eBay, and Walmart product pricing, BuyBox winner, seller count, and 90-day price history. Use when tracking retail marketplace product prices, BuyBox winner, active seller counts, and 90-day price history on Amazon, eBay, or Walmart. Do not use for checking exact warehouse stock quantities (use checkProductInventory), customer review sentiment (use getProductReviewsSentiment), or GTIN barcode specs (use lookupBarcodeEanUpc).

Input Schema

NameRequiredDescriptionDefault
product_id_or_urlYes10-character Amazon ASIN, eBay Item ID, EAN barcode, or full product listing URL.
marketplace_countryNo2-letter ISO country code for the regional marketplace (defaults to 'US').US

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / marketplace_country / default
      Added value: +"US"
    • addedInput schema / properties / marketplace_country / enum
      Added value: +[
+  "US",
+  "UK",
+  "DE",
+  "FR",
+  "JP",
+  "CA",
+  "IT",
+  "ES"
+]
    • addedInput schema / properties / marketplace_country / examples
      Added value: +[
+  "US"
+]
    • addedInput schema / properties / product_id_or_url / examples
      Added value: +[
+  "B08N5WRWNW"
+]
    • addedInput schema / properties / product_id_or_url / minLength
      Added value: +5
  2. Changed2 schema fields changed
    • changedInput schema / properties / marketplace_country / description
      Previous value: -"2-letter ISO country code for local marketplace (e.g., US, UK, DE)"New value: +"2-letter ISO country code for the regional marketplace (defaults to 'US')."
    • changedInput schema / properties / product_id_or_url / description
      Previous value: -"Amazon ASIN, eBay Item ID, EAN, or full product URL"New value: +"10-character Amazon ASIN, eBay Item ID, EAN barcode, or full product listing URL."
  3. First observed

TDQS

A4/5.0
Behavior3/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 usefully signals that pricing is live and which data points are returned, but it does not mention rate limits, data latency beyond 'live,' authentication requirements, or error behavior for missing listings. This is adequate but leaves meaningful operational gaps for a read-only pricing lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the resource and data points, and the exclusion sentence earns its place. However, the second sentence largely restates the first, repeating marketplace names and all four data points without adding new information. Removing the redundancy would make the definition tighter.

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?

This is a simple two-parameter read tool with 100% schema coverage and no output schema. The description sufficiently covers what is returned and when to use it, though it could note whether history is returned as a series or summary. The missing detail is minor given the tool's low complexity.

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 explains the ASIN/eBay ID/EAN/URL format and the marketplace_country enum with its default. The description adds no parameter-specific syntax, constraints, or examples beyond what the schema provides, making the baseline score of 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names the specific resource (product pricing), the exact marketplaces, and the included data points: BuyBox winner, seller count, and 90-day price history. This is a clear verb-plus-resource statement that an agent can distinguish from inventory, reviews, or barcode siblings without opening the schema.

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

Usage Guidelines5/5

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

The description gives explicit positive conditions (tracking marketplace product prices, BuyBox winner, seller counts, and 90-day history on Amazon, eBay, or Walmart) and explicit exclusions naming three siblings with their corresponding use cases. The routing logic to checkProductInventory, getProductReviewsSentiment, and lookupBarcodeEanUpc is unambiguous.

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

All mcp-livedatapro 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