Skip to main content
Glama

Post Listingcreate Getdata

hgr_post_listingcreate_getdata
Read-onlyIdempotent

Dedicated HGRApi tool for POST api/ListingCreate/GetData. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Resolves one supplier URL into validated product and draft-listing data for the extension's manual product flow. ownerAgent: publication. Use when: Use when the extension submits one supplier URL and needs the product details required to prepare a manual product. Input: GetDataRequest body with Url and optional extension ExtraData. AliExpress URLs may include selected variation labels and a native skuId. Header channel: current ChannelOAuthId. Admin: false. Output: Returns ProductInformation and Listing when complete product details can be obtained. AliExpress manual imports refresh the selected SKU and full variation family from the supplier even when cached product details exist. Saved product data is used only with a price checked in the last 24 hours; otherwise the import reads the supplier and keeps the saved data if that read fails. ASOS UK, Matalan and Home Bargains imports refresh supplier data when the cached or browser-extracted product has no variations; the returned product uses its selected size identity to avoid an empty parent option and retain a stable size-specific URL. Explicit ASOS UK product URLs with a selected variant preserve that exact size and avoid adding a duplicate selected-size option when the same size is already present in the variation family. Explicit AliExpress SKU selections are preserved; invalid or conflicting selections return an error instead of substituting the first variation. Variation labels remain separate from other URL parameters. A successful product response may also include OtherUrls so the client can offer an optional switch to bulk publish. A recognized product whose details cannot be obtained returns ErrorType=UnknownProduct without OtherUrls; non-product pages may return OtherUrls for bulk discovery. Admin or impersonated sessions additionally receive Debug with extraction configuration excluding cookies, intermediate product snapshots, data-source decisions and final product/draft fields. Category filling is diagnosed separately through ChannelListing/GetCategorySpecifics; browser-side changes are not observed here. Search terms: listingcreate getdata. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

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": {
      "body": "<body>",
      "channelOAuthId": "<channelOAuthId>"
    },
    "name": "hgr_post_listingcreate_getdata"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesHGRApi POST /api/ListingCreate/GetData request body.
channelOAuthIdYesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 goes well beyond them: caching rules (saved data only with a price checked in the last 24 hours, fallback to saved data on supplier read failure), per-source refresh semantics for AliExpress/ASOS UK/Matalan/Home Bargains, error contract (ErrorType=UnknownProduct without OtherUrls), and the extra Debug payload for admin or impersonated sessions. This is exactly the kind of behavior an agent cannot infer from structured fields.

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?

The purpose and usage trigger are front-loaded, but the body is a single dense run-on paragraph with semicolon-separated clauses covering many per-source edge cases. Much of the ASOS UK size-identity and variation-label detail earns its place, yet the volume and lack of structure make it hard to scan.

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 two-parameter POST tool with an output schema, everything an agent needs to call it correctly is present: the required body shape, the channel header resolution, the success and error return shapes, and the source-specific refresh caveats. No material gap remains for invocation.

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% and the schema already explains channelOAuthId, so the baseline is 3. The description adds real meaning beyond the schema's terse 'request body' entry by specifying the GetDataRequest contents (Url plus optional extension ExtraData), that AliExpress URLs may carry variation labels and a native skuId, and that variation labels stay separate from other URL parameters.

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 — resolves one supplier URL into validated product and draft-listing data for the manual product flow — and explicitly rules out the generic-endpoint reading. The 'not a generic endpoint caller' line plus the endpoint path makes it unmistakable against siblings like hgr_post_listingcreate_submit or hgr_post_catalog_getproducts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit 'Use when' trigger: the extension submits one supplier URL and needs product details to prepare a manual product. It does not, however, name the closest alternative (hgr_post_listingcreate_getdatabypsids) or state when that bulk/PSID variant should be preferred, so the routing guidance is clear but not exhaustive.

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.

Resources