Skip to main content
Glama

Supplier: Get Product Detail

get_supplier_product
Read-onlyIdempotent

[Supply Product] [What it does] Reads one supplier product's options, variants, stock, prices, shipping origins, and availability status for a given destination and language context. [When to use] Use it when the user asks about a specific supplier product's quality, stock, price, or shipping, and when the agent must verify a shortlisted candidate before importing, mapping, or quoting freight. Trigger words: this supplier product, enough stock, ships to, supply cost. [When not to use] To find candidates, use search_supplier_products. For destination freight costs, use list_supplier_product_shipping_methods_and_cost. For a product already in the store, use get_managed_store_product. [How to use]

  • Copy supplier_platform_id and supplier_product_id from the same search candidate; never use applications[].app_id or a DSers-managed product ID.

  • supplier_product_url is the usable product-detail entry; for Agent and 1688 Dropshipping it points to the configured DSers application page.

  • include_supplier_product_description defaults to false, so supplier_product_description is omitted unless explicitly requested because descriptions can be large.

  • Statuses such as NotShipTo, NotLanguage, NotDropShipping, and NotAvailable mean unavailable under the requested country or language, not that the product is missing; retry with another destination before concluding.

  • country, language, and currency are requested context only and may be unsupported upstream; report the returned values, not the requested ones.

  • Only supplier_product_variant_list[].supplier_product_variant_id is accepted for freight quotes, ordering, and mapping; stock of 0 means that variant is out of stock, not that the product is delisted.

  • Prices are strings and must be read with their currency, which can differ between variant and product level. Quotes exclude shipping, so never treat them as landed cost. [Side effects] None; read-only, and it never imports or maps a product. [Confirmation] Not required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "supplier_platform_id": "<supplier_platform_id>",
      "supplier_product_id": "<supplier_product_id>"
    },
    "name": "get_supplier_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoDestination country code for availability context (default US).US
currencyNoRequested supplier currency code. Optional.
languageNoProduct content language (default en).en
supplier_product_idYesCopy from the supplier_product_id field in search_supplier_products results. Required.
supplier_platform_idYesCopy the exact supplier platform application ID used for search_supplier_products, or use list_stores supplier_apps[].supplier_platform_id. Never guess it. Required.
include_supplier_product_descriptionNoWhether to include supplier_product_description in the response. Defaults to false because descriptions can be large.

Output Schema

NameRequiredDescriptionDefault
supplier_product_idYesSupplier product ID
supplier_platform_idYesSupplier platform application ID as a decimal string
supplier_product_urlNoSupplier product URL
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.
supplier_product_titleYesSupplier product title
supplier_product_ratingNoSupplier product rating
supplier_product_weightNoSupplier product weight
supplier_product_currencyNoSupplier currency
supplier_product_dimensionsNoSupplier product length x width x height and unit
supplier_product_media_listYesSupplier product media URLs
supplier_product_descriptionNoProduct description
supplier_product_option_listYesSupplier product options
supplier_product_order_countNoReported order count
supplier_product_weight_unitNoSupplier product weight unit
supplier_platform_category_idNoSupplier category ID
supplier_product_country_codeNoProduct country context
supplier_product_variant_listYesSupplier product variants
supplier_product_listing_statusYesSupplier product listing status
supplier_product_main_image_urlNoSupplier product main image URL
supplier_product_content_languageNoContent language
supplier_product_ship_from_country_code_listYesSupported supplier shipping-origin country codes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, yet the description still adds substantial non-obvious semantics: that NotShipTo/NotLanguage/NotDropShipping/NotAvailable are context failures rather than missing products, that country/language/currency are requests that may be ignored upstream, that stock 0 means variant-level out-of-stock, and that quotes exclude shipping. The side-effects and confirmation lines do restate the annotations, but the surrounding content is genuinely additive.

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?

The bracketed section headers front-load purpose, then usage, then caveats, and most bullets carry distinct operational information. A few lines are redundant with structured data (the default-false description flag and the read-only side-effects line), which is the only thing preventing a 5.

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?

For a six-parameter read tool with an output schema, the description covers the remaining gaps an agent would otherwise hit: which IDs are legal for downstream freight/mapping, how status codes should be interpreted, and how price strings relate to currency. Nothing needed to call it correctly or interpret failures is missing.

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

Parameters4/5

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

With 100% schema coverage the schema already documents all six parameters, so the baseline is 3; the description earns above that by explaining the trap that supplier_platform_id must never be applications[].app_id, why include_supplier_product_description defaults off (large payloads), and that country/language/currency may be unsupported upstream so returned values should be reported. The include_supplier_product_description rationale largely duplicates the schema text, keeping this just short of a 5.

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 specific verb and resource ("Reads one supplier product's options, variants, stock, prices, shipping origins, and availability status") and enumerates the exact fields returned, so the agent knows precisely what this tool produces. It is immediately distinguishable from search_supplier_products (candidate discovery) and get_managed_store_product (already-imported products).

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 when-to-use section with trigger phrases ("this supplier product", "enough stock", "ships to", "supply cost") and a when-not-to-use section that names three concrete alternatives with the condition selecting each. This is the strongest form of routing guidance in the catalog.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.