Skip to main content
Glama

MyProduct: Get Detail

get_managed_store_product
Read-onlyIdempotent

[Store Products] [What it does] Reads one DSers-managed Sales Product's options and variants, mapped Supplier Products, primary and secondary supplier-variant mappings, effective supplier inventory, blacklist state, sales-channel deletion state, and sync settings. [When to use] Use it when the user asks about one managed product's variants, inventory, pricing, mapped supplier products, or sync state, and when exact IDs are needed before a price, stock, mapping, or supplier-detail operation. [When not to use] To find, filter, or count products, use list_managed_store_products. For mapped Supplier Product content or shipping data, call get_supplier_product with the paired IDs from mapped_supplier_product_list. [How to use]

  • Copy dsers_product_id from list_managed_store_products items[].dsers_product_id; it is not a Sales Product or Supplier Product ID.

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

  • Each mapped_supplier_product_list[] entry provides the supplier_platform_id and supplier_product_id pair required by get_supplier_product.

  • primary_supplier_product_variant_mapping_list contains the default Basic Mapping supplier or the single supplier Product BFF can resolve for that sales variant. secondary_supplier_product_variant_mapping_list contains the non-default supplier returned only for Basic Mapping.

  • supplier_product_variant_display_price_amount is converted toward the DSers store default currency; always read it with supplier_product_variant_display_price_currency because Product BFF falls back to the supplier currency if conversion fails.

  • sales_product_variant_effective_supplier_inventory_list[].sales_product_variant_effective_supplier_inventory_quantity is Product BFF's final display inventory for the sales variant: primary stock first, but secondary stock is used when primary stock is zero or missing. It is not sales-channel inventory and cannot be attributed to one fixed Supplier Variant.

  • mapped_supplier_product_count of 0 means no mapped supplier summary was returned. sales_product_is_blacklisted_in_dsers comes from Product BFF is_unable; it is distinct from deletion on the sales channel. [Side effects] None; read-only. [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": {
      "dsers_store_id": "<dsers_store_id>",
      "dsers_product_id": "<dsers_product_id>"
    },
    "name": "get_managed_store_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
dsers_store_idYesCopy from list_stores response dsers_store_id field. Decimal string. Required.
dsers_product_idYesCopy from list_managed_store_products response items[].dsers_product_id field. Required.
include_sales_product_descriptionNoWhether to include sales_product_description in the response. Defaults to false because descriptions can be large.

Output Schema

NameRequiredDescriptionDefault
dsers_store_idYesRequested store ID as a decimal string
dsers_product_idYesDSers managed product ID as a decimal string
sales_channel_idYesSeller application ID as a decimal string
sales_product_urlNoSeller product URL
sales_product_titleYesProduct title
product_mapping_typeYesDSers mapping type
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.
sales_product_currencyNoSeller currency
sales_product_media_listYesProduct media URLs
sales_product_descriptionNoProduct description
sales_product_option_listYesSales product options and option values
sales_product_variant_listYesSales product variants
mapped_supplier_product_listYesSupplier Products represented by Product BFF supplier_list; excludes Basic non-default suppliers and unresolved multi-supplier Advanced variants
sales_product_main_image_urlNoMain image URL
mapped_supplier_product_countYesNumber of entries in mapped_supplier_product_list; not a count of every variant mapping
sales_product_ship_to_country_codeNoConfigured destination country
sales_product_is_blacklisted_in_dsersYesWhether the Sales Product is blacklisted in DSers; Product BFF is_unable is explicitly a blacklist flag
sales_product_is_auto_cost_sync_enabledYesAutomatic cost sync setting
sales_product_is_auto_price_sync_enabledYesAutomatic sales-price sync setting
sales_product_is_deleted_on_sales_channelYesWhether deleted on the sales channel
sales_product_is_manual_cost_sync_enabledYesManual cost sync setting
sales_product_is_manual_price_sync_enabledYesManual sales-price sync setting
sales_product_is_auto_inventory_sync_enabledYesAutomatic inventory sync setting
primary_supplier_product_variant_mapping_listYesPrimary or single resolved Supplier Product Variant mapping for each Sales Product Variant
secondary_supplier_product_variant_mapping_listYesSecondary non-default Basic Mapping Supplier Product Variant for each Sales Product Variant
sales_product_variant_effective_supplier_inventory_listYesEffective supplier inventory selected for mapped Sales Product Variants

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the 'read-only / no side effects' line is redundant. Beyond that the description discloses real derivation behavior: display price is currency-converted with a supplier-currency fallback, effective inventory prefers primary but falls back to secondary when primary is zero or missing, and blacklist state is distinct from sales-channel deletion.

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?

Well front-loaded with bracketed sections, but long: several 'How to use' bullets explain response fields (`supplier_product_variant_display_price_amount`, `mapped_supplier_product_count`, the effective-inventory list) when an output schema already exists. The ID-provenance and default-flag bullets earn their place; the field-by-field annotation of return values is padding relative to structured data.

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?

Given a read-only single-entity fetch with an output schema, the definition covers ID sourcing, default flag behavior, currency fallback, inventory resolution, blacklist-vs-deletion distinction, and the handoff path to `get_supplier_product`. Nothing an agent needs to call it correctly 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?

Schema coverage is 100%, so 3 is the baseline, but the description adds genuine meaning: `dsers_product_id` is explicitly not a Sales Product or Supplier Product ID and must be copied from `list_managed_store_products` `items[].dsers_product_id`. It also explains why `include_sales_product_description` defaults to false (descriptions can be large), which the schema only states without rationale.

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?

States a specific verb and resource ('Reads one DSers-managed Sales Product') and enumerates the exact payload: options/variants, mapped supplier products, effective inventory, blacklist and deletion state, sync settings. It also names the two siblings it is distinct from (`list_managed_store_products`, `get_supplier_product`), so an agent can separate it without reading schemas.

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?

Explicit '[When to use]' and '[When not to use]' blocks: find/filter/count goes to `list_managed_store_products`, supplier content goes to `get_supplier_product` with IDs from `mapped_supplier_product_list`. It also states the precondition role — needing exact IDs before a price, stock, mapping, or supplier-detail operation.

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.