Skip to main content
Glama
Data-Dive-Tools

DataDive MCP

Official
by Data-Dive-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Inventory Metrics and Fulfillment-Center Distribution for an ASIN

get_asin_inventory_distribution
Read-only

Retrieve Amazon ASIN stock levels, days of stock, aging and fee risks, and per-fulfillment-center unit placement. Use it to see where units sit and when stock may run out.

Instructions

Use this when the user asks about an ASIN's inventory: stock levels, days of stock or when it will run out, low-inventory or aged-inventory risk, low-inventory-level (LILF) or long-term storage (LTSF) fees, or where their units sit across Amazon's fulfillment network. Requires the Amazon sellerId (from list_seller_profiles or the user's DataDive Connections page at https://2.datadive.tools), the marketplace code, and the ASIN. Returns the metrics the DataDive Inventory page shows — fulfillableStock, totalStock, reservedStock, inboundStock, researchingStock, unfulfillableStock, daysOfStock (with daysOfStockSource AMAZON or ESTIMATE), daysOfStock30, daysOfStock90, inLowInventoryState, estWeeklyLilf, estLtsfNextAssessment, ltsfLastMonthActual, agedUnits, oldestUnitAgeDays, with fees in currency — plus totalSellableUnits and a per-FC distribution array (fc, state, availableStock, availableStockPercentage). A metric is null, never 0, when Amazon has no data (e.g. merchant-fulfilled); metrics the user's plan does not include are null and listed in lockedFields (say they need a plan upgrade, do not report them as zero). lastUpdatedAt dates the stock and metrics; distributionLastUpdatedAt dates the distribution, which is usually up to 2 days behind. Either may be null when no successful refresh happened in the last 30 days.

Input Schema

NameRequiredDescriptionDefault
asinYesAmazon Standard Identification Number (10 uppercase alphanumeric characters, e.g. B08XYZ1234).
sellerIdYesAmazon seller account ID as connected to DataDive. Get it from `list_seller_profiles`, or find it on the Connections page at https://2.datadive.tools.
marketplaceYesAmazon marketplace code, e.g. "com" for amazon.com or "co.uk" for amazon.co.uk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses critical non-obvious behavior: null-never-zero semantics, plan-gated fields surfaced via `lockedFields` with an instruction not to report them as zero, and freshness/recency behavior (distribution up to 2 days behind; both timestamps null after 30 days without a refresh). This is exactly the context annotations cannot carry.

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

Conciseness4/5

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

It is a long single block, but it is front-loaded with the trigger, then requirements, then returns, then caveats, and with no output schema the exhaustive field enumeration earns its place. Slightly dense, but no sentence is filler.

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

Completeness5/5

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

With no output schema, the description fully enumerates the return fields, the two timestamp fields and their staleness, and the null/lockedFields conventions. An agent has everything needed to call it and interpret results 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%, so the schema already documents all three parameters, including the ASIN pattern, the marketplace enum, and the sellerId source. The description restates the same sellerId provenance rather than adding new syntax or format meaning, so the baseline 3 applies.

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 description opens with a concrete verb+resource scope: an ASIN's inventory metrics and fulfillment-center distribution. It clearly distinguishes itself from siblings (rankings, niches, PPC campaigns, listing copy) by naming the exact domain — stock, days of stock, LILF/LTSF fees, per-FC distribution.

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?

It gives an explicit trigger list ("Use this when the user asks about... stock levels, days of stock, low-inventory risk, fees, or where units sit") plus the required inputs and where to obtain sellerId (`list_seller_profiles` or the Connections page). No alternative tool overlaps, so no exclusion is needed.

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

Deploy Server

Other Tools