Skip to main content
Glama

Import: Get Organization & Category Choices

get_pre_publish_product_organization
Read-onlyIdempotent

[Import List Product] [What it does] Reads current and available Organization and Category values for pre-publish products in one target store. Organization includes Collection, Type, Tags, and Vendor. [When to use] Use it when the user wants to inspect or change category, collection, tags, vendor, or URL settings before publishing. It is the normal read-and-review step before update_pre_publish_product_organization; call that Tool only when the user chooses a change. It is optional when no Organization or Category review is needed. [When not to use] For product content and variants, use get_pre_publish_product. To save actual changes, use update_pre_publish_product_organization. It is not a prerequisite for publish_products_to_stores. [How to use]

  • import_item_ids (1 to 100) and dsers_store_id are required; send the whole selection at once. Store choices are shared and each item returns its current store-specific selections.

  • For a multi-store review, call once per store and use only choices returned for that store.

  • When organizations_truncated or categories_truncated is true, narrow with organization_name, keyword, or category_keyword and re-read.

  • categories_supported=false means the platform returned no categories. select_number=0 means no declared upper limit, and is_create controls whether new values may be created.

  • Show choices to the user before applying changes. A batch read can fail per item, so inspect each failure reason and retryable flag. [Side effects] None. [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_ids": "<import_item_ids>",
      "dsers_store_id": "<dsers_store_id>"
    },
    "name": "get_pre_publish_product_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordNoOptional Organization value keyword filter. Omit to return all available values.
dsers_store_idYesThe target store ID selected by the user. Copy from list_stores response. Required.
marketplace_idNoOptional seller marketplace ID used by stores whose Category API is marketplace-specific.
import_item_idsYesAll import-list IDs selected in the user's current request, from one to 100. Send them together in one call; never split a known multi-product selection into repeated single-ID calls. Shared organization/category choices are returned once and each item includes its current store-specific selections. Paste JSON example: ["2085934367682592768"].
category_keywordNoOptional case-insensitive Category ID or name filter. Use it when categories_truncated is true.
organization_nameNoOptional exact Organization field filter, such as Type, Tags, or Vendor. Omit to return all fields.

Output Schema

NameRequiredDescriptionDefault
itemsNoPer-import-item current settings when import_item_ids is used
categoriesYesAvailable flattened category choices
organizationsYesAvailable store organization fields and values
dsers_store_idYesTarget DSers store ID
import_item_idNoImport-list item ID
categories_supportedYesTrue when the store returned category choices
categories_truncatedYesWhether matching categories were omitted; refine category_keyword when true
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.
organizations_truncatedYesWhether available Organization fields or values were omitted; refine organization_name or keyword when 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 readOnly/idempotent/non-destructive, and the description still adds non-obvious behavior: batch reads can fail per item so failure reasons and retryable flags should be inspected, truncation flags require narrowing with specific filters, `categories_supported=false` and `select_number=0` have defined meanings, and it states no side effects and no confirmation needed. The cross-store caveat (choices are store-specific; call once per store) is a real operational constraint not derivable from annotations.

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 headers (What it does / When to use / When not to use / How to use / Side effects / Confirmation) make it scannable and front-load the purpose and routing before the mechanics. It is somewhat long for a read tool, and a few lines restate schema text verbatim (the 1-to-100 and required-field notes), which is mild duplication rather than new 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 six-parameter read tool with an output schema, the description covers everything the agent needs before calling: required inputs, batching rules, per-store invocation pattern, truncation recovery, failure handling, and the temporal relationship to the update tool. Return-value shape is correctly left to the output schema rather than restated.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds semantics the schema does not: send the whole selection in one call rather than splitting, call once per store for multi-store reviews and use only that store's returned choices, and use `organization_name`/`keyword`/`category_keyword` specifically in response to the truncation flags. It also explains the relationship between `is_create` and whether new values may be created, which is behavioral meaning beyond the field type.

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?

Opens with a bracketed scope marker and a specific verb+resource: reading current and available Organization and Category values for pre-publish products in one target store, and it enumerates what 'Organization' covers (Collection, Type, Tags, Vendor). The name, title, and body all converge on one operation, and the description immediately contrasts the sibling `update_pre_publish_product_organization`, so an agent can tell the read from the write.

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?

Explicitly segments when to use (inspecting or changing category/collection/tags/vendor/URL before publishing, as the review step before the update tool), when not to use (product content and variants -> `get_pre_publish_product`; saving changes -> `update_pre_publish_product_organization`), and adds a negative prerequisite note that it is not required for `publish_products_to_stores`. It also states it is optional when no Organization/Category review is needed, which prevents reflexive calls.

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.