Skip to main content
Glama

Import: Get Item Detail

get_pre_publish_product
Read-onlyIdempotent

[Import List Product] [What it does] Reads the editable snapshot of one pre-publish product — an item on the DSers Import List page: supplier product/platform IDs, content, images, package details, options, variants, prices, stock, and the resource_version required by content and price edits. [When to use] Use it when the user asks for one pre-publish product's full detail, and whenever the agent must obtain the current version and row identifiers before editing or repricing it. Trigger words: this pre-publish product, this item in my import list, its variants, check before editing. [When not to use] To find or filter pre-publish products, use list_pre_publish_products. For a product already pushed to a store, including Draft status, use get_managed_store_product. It changes nothing. [How to use]

  • import_item_id is required and comes from list_pre_publish_products items[].import_item_id.

  • The response item.supplier_product_id and item.supplier_platform_id identify the original supplier product and platform; copy them exactly when another supplier-product Tool requires the pair.

  • include_supplier_product_description defaults to false, so both supplier_product_specifications (SPECIFICATIONS) and supplier_product_description (description body) are omitted unless explicitly requested because descriptions can be large. Set it to true to read both sections; each is returned separately without merging or rewriting the source content.

  • resource_version is the token for content edits and price edits, and it expires after each such write; re-read immediately before those writes instead of reusing an older value.

  • supplier_product_variant_id and option supplier_product_option_value_id can repeat because duplicated rows keep their supplier ID, so always pair them with variant_index or value_index.

  • Prices and costs are exact strings; send them back unchanged and never recompute or round them. Currency is reported at item and variant level.

  • If a write's outcome is unclear, re-read with this tool to confirm the current state rather than retrying the write.

  • Import List products, draft products, and pre-publish products name the same objects; accept the old wording and answer in generic product terms rather than sending the user to a page. [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": {
      "import_item_id": "<import_item_id>"
    },
    "name": "get_pre_publish_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
import_item_idYesCopy from items[].import_item_id field in list_pre_publish_products results. Required.
include_supplier_product_descriptionNoWhether to include both supplier_product_specifications (SPECIFICATIONS) and supplier_product_description (description body) in the response. Defaults to false because descriptions can be large.

Output Schema

NameRequiredDescriptionDefault
itemYesEnriched import item detail
packageYesCurrent editable product package dimensions and weight
resource_versionYesOpaque current version required by import-list update tools
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.
supplier_product_descriptionNoCurrent editable supplier product description
supplier_product_image_url_listYesCurrent ordered editable supplier product image URLs
supplier_product_specificationsNoCurrent supplier product SPECIFICATIONS section; separate from the description body; returned when include_supplier_product_description is true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, and the description consistently reinforces that with 'It changes nothing' and 'None; read-only.' It adds valuable operational behavior beyond annotations: resource_version expiration rules, re-read guidance after unclear writes, duplicate supplier ID handling with index pairing, and exact-string treatment for prices. These details materially reduce misuse risk.

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 description is structured with clear sections for what it does, when to use, when not to use, how to use, side effects, and confirmation, and the key purpose is front-loaded. It is longer than most tool descriptions, but most sentences carry actionable guidance. Slight redundancy appears between the side effects and no-change statements, keeping it below maximum conciseness.

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?

The tool has an output schema, so the description need not document every return field, but it still highlights important response elements such as supplier IDs, resource_version, omitted description sections, and repeated variant IDs. Given the tool's pre-edit complexity, the description covers the operational context an agent needs to call and interpret it correctly.

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

Parameters5/5

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

Although schema description coverage is 100%, the description adds substantial meaning beyond the schema. It explains where import_item_id comes from, why include_supplier_product_description defaults to false, that the flag returns two separate sections without merging, and how supplier IDs and repeated variant/option IDs should be used. This goes well beyond the baseline parameter documentation.

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 uses a specific verb and resource: it reads the editable snapshot of one pre-publish product on the DSers Import List page. It explicitly distinguishes this object from list/filter results and from products already pushed to a store. An agent can identify the tool without opening the schema.

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 provides explicit when-to-use guidance, including trigger phrases and the need to obtain the current version and row identifiers before editing or repricing. It also names concrete alternatives for sibling use cases: list_pre_publish_products for finding/filtering and get_managed_store_product for store products. This is near-complete routing guidance.

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.