Skip to main content
Glama

MyProduct: Get Mapping Detail

get_store_product_mapping
Read-onlyIdempotent

[Store Products] [What it does] Reads the MCP-safe saved mapping view for one DSers-managed sales product, including Basic and Advanced variant relationships, country scopes, explicit Basic option maps, and Agent relationships. Each saved supplier-variant relationship is checked against the supplier product's current variants; an invalid Basic or Advanced relationship is omitted independently without hiding another valid relationship on the same sales variant. [When to use] Use before applying Mapping changes and whenever the user wants to inspect or verify saved relationships. [When not to use] To search candidate supplier products or generate AI Mapping suggestions, use the corresponding tools; this tool never creates or updates Mapping. Use get_managed_store_product for current prices and simulate_pricing_rule for calculated prices. [How to use] Pass dsers_product_id alone, or dsers_store_id together with sales_product_id. Public mapping_type values are Basic and Advanced. basic_option_maps exposes explicit ID relationships; names are presentation only. Country arrays retain Global alongside explicit countries because Global is a fallback, not a replacement for country-specific data. The response omits the raw pool, prices, currency, ship-from, workflow fields, and any update-version token. [Side effects] None; read-only. [Confirmation] Not required.

Input Schema

NameRequiredDescriptionDefault
dsers_store_idNoConnected DSers store ID. Must always be provided together with sales_product_id.
dsers_product_idNoDSers-managed product ID as a positive decimal string. It may be provided alone, or together with the complete dsers_store_id + sales_product_id pair.
sales_product_idNoProduct ID assigned by the sales platform. Must always be provided together with dsers_store_id.

Output Schema

NameRequiredDescriptionDefault
mappingNoSaved seller-variant mappings and their nested supplier variants.
mapping_typeNoPage-aligned saved Mapping type.
product_typeNoSales product type returned by Product BFF.
dsers_product_idNoDSers-managed product ID.
basic_option_mapsNoExplicit Basic option relationships grouped by supplier product. Incomplete historical pairs retain their known fields and omit unavailable IDs.
sales_product_titleNoSales product title saved with the mapping.
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.
sales_product_main_image_urlNoSales product main image URL saved with the mapping.
sales_product_ship_to_country_codeNoDestination country code saved with this mapping.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, yet the description adds real behavioral detail: per-relationship validation against the supplier product's current variants, independent omission of invalid Basic/Advanced relationships without hiding valid ones on the same sales variant, and explicit omission of pool, prices, currency, ship-from, workflow fields and update-version tokens from the response. Minor redundancy in restating 'None; read-only' and confirmation-not-required, which the annotations already imply.

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?

Bracketed section headers keep it front-loaded and scannable, with the purpose and usage routing stated before mechanics. A few sentences are padding against the annotations (side effects 'None; read-only', 'Confirmation: Not required'), but almost every section carries distinct information.

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 read-only lookup with an output schema, the description supplies the calling shapes, response-shape expectations, per-relationship validation behavior and exclusions, so an agent can call it correctly without guessing. Nothing material about invocation or interpretation 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 the baseline is 3; the description goes further by spelling out the two accepted calling shapes (dsers_product_id alone, or dsers_store_id plus sales_product_id), the public mapping_type values Basic and Advanced, and the meaning of basic_option_maps (explicit ID relationships, names presentation-only) and country arrays retaining Global as fallback rather than replacement.

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 the saved mapping view for one DSers-managed sales product, and enumerates exactly what the view contains (Basic/Advanced variant relationships, country scopes, basic_option_maps, Agent relationships). It is clearly distinguishable from sibling tools such as get_managed_store_product and apply_product_mapping.

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 (before applying Mapping changes, or to inspect/verify saved relationships) and when-not-to-use, naming alternatives for candidate search, AI Mapping suggestions, current prices (get_managed_store_product) and calculated prices (simulate_pricing_rule). It also states the hard boundary that this tool never creates or updates Mapping.

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.