Hustle Got Real

Post Listingcreate Getdatabypsids

hgr_post_listingcreate_getdatabypsids

Read-onlyIdempotent

Dedicated HGRApi tool for POST api/ListingCreate/GetDataByPSIds. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Loads current supplier data for the exact product-source variations used during manual multi-variation product creation. ownerAgent: publication. Domain: publication. Entity: product_source_variation_data. Operation: read_and_refresh. Scope: selected_channel. Use when: Use it when the manual product form needs price, stock, EAN and source images for a known set of exact ProductSourceIds, especially before displaying or publishing all supplier variations. Do not use it to discover products or variations without exact ProductSourceIds, or for existing store-listing collection or ranking. Input: [FromBody] rq: GetDataByPSIdsRequest. Main fields: ProductSourceIds: int[]. Header channel: current ChannelOAuthId. Admin: false. Output: Returns ProductSources keyed by the requested ProductSourceId, with available images, price, stock and EAN. Cached stock is read from saved supplier stock options. Matalan and Home Bargains sizes are refreshed with live stock information, including zero stock for unavailable sizes. Sources configured for live refresh return non-empty freshly scraped images immediately; cached images are retained only when the refresh supplies no images. Requested AliExpress variation URLs using a readable selection, a numeric skuId/sku_id, or both together, without a saved supplier SKU are refreshed to resolve that exact variation and load its images. These AliExpress child refreshes obtain stock information and return refreshed data only after the supplier identity, price and available stock have been saved. If the supplier identity, price or available stock cannot be confirmed, or saving fails, the response retains cached data. Bare AliExpress product URLs are not refreshed by this recovery rule. The refresh can also update stored product-source data. Search terms: listingcreate getdatabypsids. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

Input Schema

Name	Required	Description	Default
`body`	Yes	HGRApi POST /api/ListingCreate/GetDataByPSIds request body.
`channelOAuthId`	Yes	ChannelOAuthId returned by hgr_list_channels for the selected visible store.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A3.5/5.0

Behavior1/5

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

The description discloses substantial behavior (cached stock vs. live refresh for Matalan/Home Bargains, AliExpress variation recovery, fallback to cached data on failure), but it also states 'The refresh can also update stored product-source data' while annotations declare readOnlyHint=true. A mutating side effect contradicts the declared read-only contract, so per the rubric this is scored as a contradiction despite the otherwise rich disclosure.

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?

Key routing info (purpose, use-when, do-not-use) is front-loaded, but the body is padded with internal metadata (ownerAgent, Domain, Entity, Operation, Scope, 'Search terms:', endpoint boilerplate) that is redundant against the tool name and schema. Roughly a third of the text could be removed without losing call-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover safety, so the description does not need to restate return shapes; it nonetheless explains keyed-by-ProductSourceId results, live vs. cached image/stock behavior, and failure fallbacks. The remaining gap is that the read-only vs. side-effect ambiguity is never reconciled for the agent.

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, and the description adds meaning: ProductSourceIds are 'exact' variation identifiers (int[]) taken from the manual form, and the channel header is the current ChannelOAuthId. It stops short of format/size limits or what an empty array does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: loads current supplier data (price, stock, EAN, images) for exact ProductSourceIds during manual multi-variation product creation. It implicitly separates itself from hgr_post_listingcreate_getdata and the listing-collection tools, though it never names those siblings explicitly.

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 'Use when' clause (manual product form needing price/stock/EAN/images for a known set of exact ProductSourceIds) plus an explicit 'Do not use it to...' exclusion covering discovery and existing store-listing collection/ranking. This is exactly the when/when-not/alternative structure the dimension rewards.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hustle Got Real tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?