Skip to main content
Glama

get_fba_inventory

Get FBA inventory levels by SKU or ASIN. Includes fulfillable, unfulfillable, reserved, inbound, and AWD quantities.

Instructions

Read FBA inventory levels by SKU/ASIN, including fulfillable, unfulfillable, reserved, inbound, and AWD quantities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:109-239 (registration)
    Registration of the 'get_fba_inventory' tool in the tools array. The tool has an empty input schema (no parameters) and is described as reading FBA inventory levels by SKU/ASIN.
      // --- Inventory ---
      {
        name: "get_fba_inventory",
        description:
          "Read FBA inventory levels by SKU/ASIN, including fulfillable, unfulfillable, reserved, inbound, and AWD quantities.",
        inputSchema: { type: "object", properties: {}, additionalProperties: false },
      },
      {
        name: "get_inventory_health",
        description:
          "Read FBA inventory health scoring with stranded, aged, excess, and low-stock indicators per ASIN.",
        inputSchema: { type: "object", properties: {}, additionalProperties: false },
      },
      {
        name: "get_orders",
        description:
          "Read recent Amazon orders with status, marketplace, totals, items, and shipping details.",
        inputSchema: dateRangeSchema,
      },
      {
        name: "get_sales_velocity",
        description:
          "Read sales velocity by ASIN: 7/30/90-day rolling units sold, days of cover, and sell-through pace.",
        inputSchema: { type: "object", properties: {}, additionalProperties: false },
      },
      {
        name: "get_inventory_risk_triage",
        description:
          "Read prioritized inventory risk: stockouts, excess, aged inventory, suppressed listings, and Buy Box loss with risk_level and coverage_state.",
        inputSchema: { type: "object", properties: {}, additionalProperties: false },
      },
    
      // --- Catalog ---
      {
        name: "get_product_details",
        description:
          "Read catalog metadata for an ASIN: title, brand, category, dimensions, images, and identifiers.",
        inputSchema: {
          type: "object" as const,
          properties: { asin: { type: "string", description: "Amazon ASIN." } },
          required: ["asin"],
          additionalProperties: false,
        },
      },
      {
        name: "get_listing_quality",
        description:
          "Read listing quality scoring: title length, bullet completeness, A+ Content presence, image count, and suppressed-status flags per ASIN.",
        inputSchema: { type: "object", properties: {}, additionalProperties: false },
      },
      {
        name: "get_variations",
        description:
          "Read variation family relationships (parent ASIN with all child ASINs) including variation theme.",
        inputSchema: {
          type: "object" as const,
          properties: { parent_asin: { type: "string" } },
          required: ["parent_asin"],
          additionalProperties: false,
        },
      },
    
      // --- Finance ---
      {
        name: "get_profitability",
        description:
          "Read net profitability by ASIN: gross sales minus FBA fees, referral fees, ad spend, COGS, and returns.",
        inputSchema: dateRangeSchema,
      },
      {
        name: "get_fee_breakdown",
        description:
          "Read Amazon fee breakdown for an ASIN: referral fees, FBA fees, storage fees, and dimensional weight estimates.",
        inputSchema: {
          type: "object" as const,
          properties: { asin: { type: "string" } },
          required: ["asin"],
          additionalProperties: false,
        },
      },
      {
        name: "get_settlement_economics",
        description:
          "Read settlement-period unit economics: starting balance, charges, deposits, refunds, and reserves.",
        inputSchema: dateRangeSchema,
      },
    
      // --- Ranking ---
      {
        name: "get_current_rank",
        description:
          "Read live keyword rank for an ASIN: organic position, sponsored position, and total result count.",
        inputSchema: {
          type: "object" as const,
          properties: {
            asin: { type: "string" },
            keyword: { type: "string" },
          },
          required: ["asin", "keyword"],
          additionalProperties: false,
        },
      },
    
      // --- Fulfillment ---
      {
        name: "get_shipping_preview",
        description:
          "Read MCF (Multi-Channel Fulfillment) shipping cost and speed estimates for a destination address.",
        inputSchema: { type: "object", properties: {}, additionalProperties: false },
      },
    
      // --- Utility ---
      {
        name: "create_shareable_report",
        description:
          "Create a public, read-only snapshot URL of an MCP tool result so a stakeholder without an account can view it.",
        inputSchema: {
          type: "object" as const,
          properties: { title: { type: "string" } },
          additionalProperties: false,
        },
      },
    
      // --- Setup helper ---
      {
        name: "agentcentral_setup",
        description:
          "Returns the connection details and setup link for the hosted agentcentral MCP server.",
        inputSchema: { type: "object", properties: {}, additionalProperties: false },
      },
    ]
  • Input schema for get_fba_inventory - empty object, no parameters required.
      inputSchema: { type: "object", properties: {}, additionalProperties: false },
    },
Behavior2/5

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

The word 'Read' implies non-destructiveness, but there are no annotations to confirm. The description lists included data but omits aspects like data freshness, pagination, or scope (all inventory vs filtered).

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?

Single sentence, well-structured, no fluff. Though concise, the misleading content reduces effectiveness.

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

Completeness2/5

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

With no parameters or output schema, the description should clarify the return structure and any limitations. It lists data fields but fails to explain whether the call returns all inventory or requires identifiers. Lacks context relative to sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero parameters, and the description incorrectly implies filtering by SKU/ASIN. This contradicts the schema and confuses parameter usage.

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

Purpose3/5

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

The description clearly states it reads FBA inventory levels and lists specific data types. However, it claims filtering 'by SKU/ASIN' yet the input schema has no parameters, creating ambiguity.

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?

No guidance on when to use this tool versus alternatives like get_inventory_health or get_inventory_risk_triage. The agent gets no decision support.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentcentral-to/agent-central-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server