Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hustle Got Real

REMOTE · MCP.HUSTLEGOTREAL.COM

Dropshipping for eBay, Amazon and Shopify: products, listings, prices, stock, orders and analytics.

+3 this week 57 Trust /100

Last scanned (19 hours ago)

Scores higher than 43% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability0
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 34974 tokens (~202/item across 173 items; 172 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety50
  • Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "Do not tell the user", at byte 6308 of that field. See how to fix → Fail
  • All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 174 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “hgr_post_searchproduct_recoverlisting”, which the server declares destructive security
    • New tool “hgr_post_searchproduct_recoverlistings”, which the server declares destructive security
    • Tool “hgr_get_searchproduct_getmissinglistings” rewrote its description, which is the text the model reads security
    • Server version: 2026.11.1.0 → 2026.11.3.1 functional
  • 2 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “hgr_post_listingcreate_getdata” rewrote its description, which is the text the model reads security
    • Server version: 2026.10.31.0 → 2026.11.1.0 functional
  • 1 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “hgr_post_sales_loadprogress” rewrote its description, which is the text the model reads security
    • Server version: 2026.10.29.1 → 2026.10.31.0 functional
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 2026.10.29.0 → 2026.10.29.1 functional
  • 29 Oct 26 54

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.hustlegotreal.com/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=partner.hustlegotreal.com CN=YR2,O=Let's Encrypt,C=US 21 Oct 2026 19 Jan 2027 RSA 2048 SHA256-RSA 573b203bf16fc63dfaee0ed17cb4f2756ac
SANs: mcp.hustlegotreal.com, partner.hustlegotreal.com, partnerapi.hustlegotreal.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.hustlegotreal.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
hustlegotreal.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.hustlegotreal.com/ Not MCP 200
http (plaintext) http://mcp.hustlegotreal.com/ HTTPS enforced 308 https://mcp.hustlegotreal.com/
MCP tools · 172 exposed · ~31,732 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
hgr_post_channellisting_list ~260

Dedicated HGRApi tool for POST api/ChannelListing/List. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Resolves one supplier product URL into validated product data for listing creation. ownerAgent: publication. Use when: Use when a user has submitted one concrete supplier product URL and needs the product data required to prepare a listing. Input: ListRequest body with Url and optional extension ExtraData. Header channel: current ChannelOAuthId. Output: Returns ComListing with validated product data when details can be obtained. A successful product response may also include OtherUrls so compatible extension clients can offer an optional switch to bulk publish. For a recognized product URL whose details cannot be obtained, returns Success=false with ErrorType=UnknownProduct without OtherUrls. Non-product pages may return OtherUrls for bulk discovery. Search terms: channellisting list. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/ChannelListing/List request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_channellisting_monitorexistinglisting ~346

Dedicated HGRApi tool for POST api/ChannelListing/MonitorExistingListing. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Imports or monitors existing channel listings in HGR. Imported listings are always activated. ownerAgent: publication. Use when: Use when concrete existing store listing/product ids and source URLs are already selected and the user wants HGR to monitor/import those existing listings. Input: [FromBody] model: AddListingModel. Main fields: OAuthId: int, Listings: ListingToMonitor[]. Header channel: current ChannelOAuthId. ToRelist is currently ignored. UserDevice is optional HGRWeb client telemetry; AI chat and MCP must omit it and must not invent a device value. Output: Returns import/monitoring results with inserted, invalid, repeated and quota-related entries. Imported eBay API variations preserve VAT when the store supplies it; unknown VAT is not inferred from the publication default. Search terms: channellisting monitorexistinglisting. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally. Internal-only request fields are removed automatically before the HGRApi request is sent.

NameTypeReqDescription
body–yesHGRApi POST /api/ChannelListing/MonitorExistingListing request body. Internal-only request fields are removed automatically.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_channellisting_monitorexistinglisting2 ~432

Dedicated HGRApi tool for POST api/ChannelListing/MonitorExistingListing2. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Imports existing store products into HGR with live progress over one HTTP stream. Imported products are activated; no new marketplace adverts are published. ownerAgent: publication. Use when: Use when exact existing store product ids and supplier URLs are selected and the caller can keep an SSE response open. Send the entire selection in one request. Do not use for catalog discovery or new marketplace publication. Input: Authenticated, not admin-only. Body: AddListingModel with Listings containing Id, SourceURL and optional VariationSku, VariationAttributes, SourceVariation, SourceWarehouse, Markup and Title. Requires Header channel: authorized ChannelOAuthId; the body OAuthId does not override it. ToRelist is ignored. UserDevice is optional web telemetry; AI and MCP must omit it. Output: SSE progress events contain phase, total, processed, imported, alreadyExisting, rejected, failed and optional itemId, error, pages, totalPages and cachedProducts. The terminal completed event contains inserted, wereInYourHGR, repeated, emptyUrl, notValidUrl, failed (id, variationSku, error), total, processed, ok and error. Inspect ok, failed and processed/total; a terminal event alone does not mean all products were imported. An unexpected stream failure emits error. Search terms: monitorexistinglisting 2, channellisting monitorexistinglisting 2. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/ChannelListing/MonitorExistingListing2 request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_channellisting_optimizeimage ~240

Dedicated HGRApi tool for POST api/ChannelListing/OptimizeImage. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST optimize image operation in published product creation and optimization. Use when: Use it when a client needs to run the optimize image operation for published product creation and optimization. Input: rq: OptimizeImageRequest. Main fields: ImageUrl: string, Action: AIActionType, Settings: Setting[]. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the optimize image operation. Search terms: channellisting optimizeimage. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/ChannelListing/OptimizeImage request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_channellisting_optimizespecificfields ~247

Dedicated HGRApi tool for POST api/ChannelListing/OptimizeSpecificFields. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST optimize specific fields operation in published product creation and optimization. Use when: Use it when a client needs to run the optimize specific fields operation for published product creation and optimization. Input: rq: OptimizeSpecificFieldsRequest. Main fields: ProductSourceId: int, Fields: ChannelSpecificField[]. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the optimize specific fields operation. Search terms: channellisting optimizespecificfields. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/ChannelListing/OptimizeSpecificFields request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_dispatch_getshipmentdetails ~159

Dedicated HGRApi tool for POST api/Dispatch/GetShipmentDetails. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST get shipment details operation in shipping and dispatch operations. Use when: Use it when a client needs to run the get shipment details operation for shipping and dispatch operations. Input: [FromBody] request: GetShipmentDetailsRequest. Main fields: TrackingCode: string. Output: Returns the result or applies the effect of the get shipment details operation. Search terms: dispatch getshipmentdetails. Send the exact request payload in body.

NameTypeReqDescription
body–yesHGRApi POST /api/Dispatch/GetShipmentDetails request body.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_dispatch_updateshipmentdetails ~203

Dedicated HGRApi tool for POST api/Dispatch/UpdateShipmentDetails. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST update shipment details operation in shipping and dispatch operations. Use when: Use it when a client needs to run the update shipment details operation for shipping and dispatch operations. Input: [FromBody] request: VelociPackerShipmentUpdateRequest. Main fields: TrackingCode: string, OrderReference: string, DeliveredOn: DateTime. Output: Returns the result or applies the effect of the update shipment details operation. Search terms: dispatch updateshipmentdetails. Send the exact request payload in body. Requires confirmed=true before execution.

NameTypeReqDescription
body–yesHGRApi POST /api/Dispatch/UpdateShipmentDetails request body.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_helpcentre_contact ~259

Dedicated HGRApi tool for POST api/HelpCentre/Contact. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Creates a legacy authenticated help-centre contact ticket. Domain: support. Entity: support_ticket. Operation: create. Scope: authenticated_user. Use when: Use for legacy contact form submissions where a visible ticket id is not required. AIChat must prefer Contact2 when it needs to show the created ticket reference/link. Input: rq: ContactModel. Main fields: Message: string, Attachments: Attachment[]. Optional X-HGR-Client: ai_chat identifies the HGR AI chat gateway; normal web requests omit it. Output: Boolean success flag only. It does not return a visible ticket id. The creation event actor is human for web submissions or ai_chat for HGR AI chat; the first message remains an inbound customer message. Search terms: helpcentre contact. Send the exact request payload in body. Requires confirmed=true before execution.

NameTypeReqDescription
body–yesHGRApi POST /api/HelpCentre/Contact request body.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listing_autolist ~223

Dedicated HGRApi tool for POST api/Listing/AutoList. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST auto list operation in bulk publication and publication tracking. Use when: Use it when a client needs to run the auto list operation for bulk publication and publication tracking. Input: request: AutoListRequest. Main fields: WeListForYou: bool. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the auto list operation. Search terms: listing autolist. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Listing/AutoList request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listing_getbulkhistory ~223

Dedicated HGRApi tool for POST api/Listing/GetBulkHistory. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Returns recent bulk publication jobs and their recorded status/errors for the selected store. ownerAgent: publication. Use when: Use it to inspect bulk publication history and diagnose a job's recorded error. Input: Optional AutoListRequest. Header channel: current ChannelOAuthId. Output: Returns logs with job status, error code, listing status and origin. EnumValues maps the numeric codes. ChannelListingStatusFlags is a bitmask: decode every set bit, not the whole number as one ordinal. Search terms: listing getbulkhistory. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Listing/GetBulkHistory request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listing_getscrapingconfig ~223

Dedicated HGRApi tool for POST api/Listing/GetScrapingConfig. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Returns supplier page extraction settings for the listing extension and bulk publication. Use when: Use it to identify product details and product links from a supported supplier page. Input: rq: GetScrapingConfigRequest. Main fields: Url: string, Site: eCountry?. Header channel: current ChannelOAuthId; Site defaults to the current store country. Output: Returns supplier-specific extraction settings. Keeps a configured product-link selector; uses all page links only when no link selector is configured. Search terms: listing getscrapingconfig. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Listing/GetScrapingConfig request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listing_migratebulk ~360

Dedicated HGRApi tool for POST api/Listing/MigrateBulk. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Queues selected listings for migration to a target channel in bulk. ownerAgent: publication. Use when: Use when concrete listing ids and a target channel are already selected and the user wants to migrate/copy them in bulk. Input: data: MigrateBulkRequest. Main fields: ListingIds: int[], TargetId: int, listFrequencyMinutes: int, dontListUntil: DateTime?, reviewBeforePublishing: bool, createdBy: int, ignoreVero: bool, ignoreOOS: bool, optimizeTitle: bool, optimizeDescription: bool, optimizeFields: bool. Header channel: current ChannelOAuthId. UserDevice is optional HGRWeb client telemetry; AI chat and MCP must omit it and must not invent a device value. Output: Creates migration bulk jobs for the selected listing ids. Search terms: listing migratebulk. Send the exact request payload in body. Requires confirmed=true and impactConfirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally. Internal-only request fields are removed automatically before the HGRApi request is sent.

NameTypeReqDescription
body–yesHGRApi POST /api/Listing/MigrateBulk request body. Internal-only request fields are removed automatically.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listing_partner ~216

Dedicated HGRApi tool for POST api/Listing/Partner. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST partner operation in bulk publication and publication tracking. Use when: Use it when a client needs to run the partner operation for bulk publication and publication tracking. Input: request: AutoListRequest. Main fields: WeListForYou: bool. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the partner operation. Search terms: listing partner. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Listing/Partner request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listing_relistedbulk2 ~339

Dedicated HGRApi tool for POST api/Listing/RelistedBulk2. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Queues selected existing listings for relisting in bulk. ownerAgent: publication. Use when: Use when concrete listing ids are already selected and the user wants to relist them in bulk. Input: data: RelistedBulk2Request. Main fields: ListingIds: int[], listFrequencyMinutes: int, dontListUntil: DateTime?, reviewBeforePublishing: bool, createdBy: int, ignoreVero: bool, ignoreOOS: bool, optimizeTitle: bool, optimizeDescription: bool, optimizeFields: bool. Header channel: current ChannelOAuthId. UserDevice is optional HGRWeb client telemetry; AI chat and MCP must omit it and must not invent a device value. Output: Creates relist bulk jobs for the selected listing ids. Search terms: relistedbulk 2, listing relistedbulk 2. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally. Internal-only request fields are removed automatically before the HGRApi request is sent.

NameTypeReqDescription
body–yesHGRApi POST /api/Listing/RelistedBulk2 request body. Internal-only request fields are removed automatically.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listing_saveautolist ~399

Dedicated HGRApi tool for POST api/Listing/SaveAutolist. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Saves a bulk/autolist publication batch. ownerAgent: publication. Use when: Use when the user wants to queue multiple source URLs for publication or review through the autolist/bulk listing flow. Input: data: SaveAutolistRequest. Main fields: listings: string[][], listFrequencyMinutes: int, dontListUntil: DateTime?, reviewBeforePublishing: bool, createdBy: int, ignoreVero: bool, ignoreOOS: bool, optimizeTitle: bool, optimizeDescription: bool, optimizeFields: bool, publishVariations: bool, WeListForYou: bool, GeneratorId: int?. Each listings row is [sourceUrl] or [sourceUrl, optionalTitle]. sourceUrl is required; an omitted, null or empty title means no custom title is supplied. A supplied title is preserved. Header channel: current ChannelOAuthId. UserDevice is optional HGRWeb client telemetry; AI chat and MCP must omit it and must not invent a device value. Output: Creates bulk listing jobs and returns an AutolistSummaryViewModel with processed, duplicated, invalid and quota-related counts. Search terms: listing saveautolist. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally. Internal-only request fields are removed automatically before the HGRApi request is sent.

NameTypeReqDescription
body–yesHGRApi POST /api/Listing/SaveAutolist request body. Internal-only request fields are removed automatically.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listing_savebulkpublish ~532

Dedicated HGRApi tool for POST api/Listing/SaveBulkPublish. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Saves a batch of URLs for bulk publication and returns one result per line. ownerAgent: publication. SearchTerms: save bulk publish, bulk publish, bulk publishing, mass publication, publicar en bulk. Use when: Use it when the client needs to know exactly which line was processed and which line was rejected without summarizing only by counts. Use it when selected products are source product URLs, Amazon URLs, ASIN URLs converted to source URLs, or source-page URLs. Do not use it to get existing listings or search candidates. Input: data: SaveAutolistRequest. Main fields: listings: string[][], listFrequencyMinutes: int, dontListUntil: DateTime?, reviewBeforePublishing: bool, createdBy: int, ignoreVero: bool, ignoreOOS: bool, optimizeTitle: bool, optimizeDescription: bool, optimizeFields: bool, publishVariations: bool, WeListForYou: bool. listings is string[][] where each row is [sourceUrl, optionalTitle]; sourceUrl is the supplier/source product URL to publish. Use reviewBeforePublishing for pending review, optimizeTitle/optimizeDescription/optimizeFields for optimization choices, and listFrequencyMinutes/dontListUntil for delayed publication. Do not send CatalogSubmitRequest.ProductsToList here. Header channel: current ChannelOAuthId. Internal client fields are managed by the tool and are not tool inputs. Output: Returns SaveBulkPublishLineStatus[] in the same order as listings. Values: Processed, ForbiddenWordsUrl, DuplicatedUrl, InvalidUrl, InvalidSourceUrl, ExistingListing, NoQuota, InvalidGenerator or DuplicatedProductSource. Search terms: listing savebulkpublish. Send the exact request payload in body. Requires confirmed=true and impactConfirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally. Internal-only request fields are removed a…

NameTypeReqDescription
body–yesHGRApi POST /api/Listing/SaveBulkPublish request body. Internal-only request fields are removed automatically.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listingcreate_editpending ~223

Dedicated HGRApi tool for POST api/ListingCreate/EditPending. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST edit pending operation in manual product creation. Use when: Use it when a client needs to run the edit pending operation for manual product creation. Input: [FromBody] rq: EditPendingRequest. Main fields: ListingId: int. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the edit pending operation. Search terms: listingcreate editpending. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/ListingCreate/EditPending request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listingcreate_getdata ~496

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…

NameTypeReqDescription
body–yesHGRApi POST /api/ListingCreate/GetData request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listingcreate_getdatabypsids ~475

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: li…

NameTypeReqDescription
body–yesHGRApi POST /api/ListingCreate/GetDataByPSIds request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_listingcreate_submit ~377

Dedicated HGRApi tool for POST api/ListingCreate/Submit. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Submits a manually prepared listing for creation. ownerAgent: publication. Use when: Use only after manual listing creation data has already been prepared and the user wants to create or queue that exact listing. Input: [FromBody] rq: SubmitCreateRequest, compatible with CreateRequest. Variation Markup settings are rounded to the nearest integer, with midpoint values rounded away from zero. Non-finite, malformed or out-of-range Markup values are ignored without deleting an existing override. For eBay API only, a missing VAT variation setting is initialized from the saved draft VAT or the store's PublishVAT default. Explicit product VAT, including zero, is preserved. VAT must be an integer from 0 to 100. UserDevice is optional HGRWeb client telemetry; AI chat and MCP must omit it and must not invent a device value. Output: Creates the listing through ListingService and returns success. Search terms: listingcreate submit. Send the exact request payload in body. Requires confirmed=true and impactConfirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally. Internal-only request fields are removed automatically before the HGRApi request is sent.

NameTypeReqDescription
body–yesHGRApi POST /api/ListingCreate/Submit request body. Internal-only request fields are removed automatically.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_notificationcenter_getall ~192

Dedicated HGRApi tool for POST api/NotificationCenter/GetAll. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST get all operation in notification centre operations. Use when: Use it when a client needs to run the get all operation for notification centre operations. Input: rq: GetAllRequest. Main fields: Page: int. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the get all operation. Search terms: notificationcenter getall. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/NotificationCenter/GetAll request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_notificationcenter_markallasread ~217

Dedicated HGRApi tool for POST api/NotificationCenter/MarkAllAsRead. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST mark all as read operation in notification centre operations. Use when: Use it when a client needs to run the mark all as read operation for notification centre operations. Input: No explicit input parameters required. Output: Returns the result or applies the effect of the mark all as read operation. Search terms: notificationcenter markallasread. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/NotificationCenter/MarkAllAsRead request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_notificationcenter_markallchannelasread ~228

Dedicated HGRApi tool for POST api/NotificationCenter/MarkAllChannelAsRead. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST mark all channel as read operation in notification centre operations. Use when: Use it when a client needs to run the mark all channel as read operation for notification centre operations. Input: Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the mark all channel as read operation. Search terms: notificationcenter markallchannelasread. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/NotificationCenter/MarkAllChannelAsRead request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_notificationcenter_markasread ~221

Dedicated HGRApi tool for POST api/NotificationCenter/MarkAsRead. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST mark as read operation in notification centre operations. Use when: Use it when a client needs to run the mark as read operation for notification centre operations. Input: rq: MarkAsReadRequest. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the mark as read operation. Search terms: notificationcenter markasread. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/NotificationCenter/MarkAsRead request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_sales_fixedorderline ~275

Dedicated HGRApi tool for POST api/Sales/FixedOrderLine. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Completes an exact order line that is in CompletedAutoOrderPending. ownerAgent: orders-autoordering. Domain: orders. Entity: order_line. Operation: complete_pending_autoorder. Scope: current_store. Use when: Use only for an exact order line whose current state is CompletedAutoOrderPending and the user confirms the corresponding visible Mark as Purchased action. Input: [FromBody] rq: LoadAddressesFromOrderLineRequest. Main fields: OrderLineIds: int[]. Required Header channel: current ChannelOAuthId. Output: Moves eligible CompletedAutoOrderPending lines to CompletedAutoOrder and returns refreshed order data. Search terms: sales fixedorderline. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Sales/FixedOrderLine request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_sales_forceprocessorderline ~264

Dedicated HGRApi tool for POST api/Sales/ForceProcessOrderLine. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST force process order line operation in sales/order operations. Use when: Use it when a client needs to run the force process order line operation for sales/order operations. Input: [FromBody] rq: LoadAddressesFromOrderLineRequest. Main fields: OrderLineIds: int[]. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the force process order line operation. Search terms: sales forceprocessorderline. Send the exact request payload in body. Requires confirmed=true and impactConfirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Sales/ForceProcessOrderLine request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_sales_generatetrackingid ~322

Dedicated HGRApi tool for POST api/Sales/GenerateTrackingId. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Generates an HGR/VelociPacker tracking number for exact existing order lines that have already been processed or marked as purchased. ownerAgent: orders-autoordering. Domain: orders. Entity: order_line. Operation: generate_tracking. Scope: current_store. Use when: Use it when the user explicitly asks HGR to generate tracking for an existing order. A manually purchased supplier order must first be marked as purchased in HGR; in HGRWeb the user then clicks Generate it in Orders. Input: [FromBody] rq: LoadAddressesFromOrderLineRequest. Main fields: OrderLineIds: int[]. Required Header channel: current ChannelOAuthId. Output: Queues HGR/VelociPacker tracking generation for each supplied order line and returns refreshed order data on success or the processing result when generation cannot start. Search terms: sales generatetrackingid. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Sales/GenerateTrackingId request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_sales_loadaddressesfromorderline ~220

Dedicated HGRApi tool for POST api/Sales/LoadAddressesFromOrderLine. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST load addresses from order line operation in sales/order operations. Use when: Use it when a client needs to run the load addresses from order line operation for sales/order operations. Input: [FromBody] rq: LoadAddressFromOrderLineRequest. Main fields: OrderLineId: int. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the load addresses from order line operation. Search terms: sales loadaddressesfromorderline. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Sales/LoadAddressesFromOrderLine request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_sales_loadprogress ~314

Dedicated HGRApi tool for POST api/Sales/LoadProgress. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Reads the auto-ordering progress of one exact order line. ownerAgent: orders-autoordering. Domain: orders. Entity: order_line. Operation: get_progress. Scope: current_store. Use when: Use it to see the auto-ordering states of an existing order line, for example to explain why an automatic purchase failed. Input: [FromBody] rq: LoadProgressRequest. Main fields: Id: int. Header channel: current ChannelOAuthId. Output: Returns states (id, date, status, error, errorMessage), lastStatus, lastStatusUpdate and lastAccountAlias. errorMessage is null for most errors. It is returned for CandBeMarkedAsDisparched errors and for OutOfStock errors whose text starts with No eligible new offer. That text means auto-ordering refused the order because the supplier has no offer in new condition, so nothing was bought; the text after Refused conditions: lists the conditions it found. Search terms: sales loadprogress. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Sales/LoadProgress request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_sales_manuallydispatchorderline ~302

Dedicated HGRApi tool for POST api/Sales/ManuallyDispatchOrderLine. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Records exact existing order lines as manually purchased in HGR. This is the HGRWeb Mark as Purchased action for normal manual-purchase states. ownerAgent: orders-autoordering. Domain: orders. Entity: order_line. Operation: mark_purchased. Scope: current_store. Use when: Use only after the user confirms that they already placed the real supplier order manually and wants to record that purchase in HGR before generating HGR/VelociPacker tracking. Input: [FromBody] rq: LoadAddressesFromOrderLineRequest. Main fields: OrderLineIds: int[]. Required Header channel: current ChannelOAuthId. Output: Changes eligible order lines to the manually purchased state and returns refreshed order data. Search terms: sales manuallydispatchorderline. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Sales/ManuallyDispatchOrderLine request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_sales_markasdispatched ~279

Dedicated HGRApi tool for POST api/Sales/MarkAsDispatched. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Acknowledges in HGR that an order-dispatch warning was handled manually for one exact order line. ownerAgent: orders-autoordering. Domain: orders. Entity: order_line. Operation: acknowledge_manual_dispatch. Scope: current_store. Use when: Use only when the user explicitly wants to clear the HGR warning after manually handling dispatch in the marketplace. Input: [FromBody] rq: AddAutoOrderReferenceRequest. Main field: OrderLineId: int. Required Header channel: current ChannelOAuthId. Output: Marks the dispatch warning as acknowledged in HGR and returns whether the order line was updated. Search terms: sales markasdispatched. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Sales/MarkAsDispatched request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_sales_processorderline ~262

Dedicated HGRApi tool for POST api/Sales/ProcessOrderLine. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Starts automatic supplier purchase processing for exact existing order lines using the current saved auto-ordering settings. ownerAgent: orders-autoordering. Use when: Use it when the user explicitly wants to process or retry an existing order after correcting a payment card or another auto-ordering setting. Input: [FromBody] rq: LoadAddressesFromOrderLineRequest. Main fields: OrderLineIds: int[]. Required Header channel: current ChannelOAuthId. Output: Attempts normal processing for each supplied order line and returns refreshed order data on success or the processing error result. Search terms: sales processorderline. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Sales/ProcessOrderLine request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_sales_stoporderline ~232

Dedicated HGRApi tool for POST api/Sales/StopOrderLine. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST stop order line operation in sales/order operations. Use when: Use it when a client needs to run the stop order line operation for sales/order operations. Input: [FromBody] rq: LoadAddressesFromOrderLineRequest. Main fields: OrderLineIds: int[]. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the stop order line operation. Search terms: sales stoporderline. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/Sales/StopOrderLine request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_defaultsettingsmultiple ~237

Dedicated HGRApi tool for POST api/SearchProduct/DefaultSettingsMultiple. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST default settings multiple operation in existing published product/listing management. Use when: Use it when a client needs to run the default settings multiple operation for existing published product/listing management. Input: [FromBody] rq: RemoveMultipleListingRequest. Main fields: Ids: int[]. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the default settings multiple operation. Search terms: searchproduct defaultsettingsmultiple. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/SearchProduct/DefaultSettingsMultiple request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_getlistingsimages ~225

Dedicated HGRApi tool for POST api/SearchProduct/getListingsImages. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Returns the first image of active listings for concrete publication ids. ownerAgent: listings. Domain: listings. Entity: exact_listing. Operation: get_exact. Scope: current_store. Use when: Use it only when concrete listingIds are already known and thumbnails are needed for those exact listings. Input: Header channel: current ChannelOAuthId and body int[] with concrete listingIds. Does not accept free search or store scans. Output: Returns a map from published product id to image URLs. Search terms: searchproduct getlistingsimages. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/SearchProduct/getListingsImages request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_getpendinglistingsimages2 ~240

Dedicated HGRApi tool for POST api/SearchProduct/getPendingListingsImages2. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST get pending listings images2 operation in existing published product/listing management. Use when: Use it when a client needs to run the get pending listings images2 operation for existing published product/listing management. Input: [FromBody] listings: GetPendingListingsImages2Request[]. Main fields: Id: int, SourceId: int. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the get pending listings images2 operation. Search terms: getpendinglistingsimages 2, searchproduct getpendinglistingsimages 2. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/SearchProduct/getPendingListingsImages2 request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_listnow ~430

Dedicated HGRApi tool for POST api/SearchProduct/ListNow. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Retries a failed pending publication or submits a pending product now. Domain: listings. Entity: pending_listing. Operation: retry_or_publish. Scope: current_store. State: pending. RequiredInputs: confirmed. ownerAgent: publication. SupportingAgents: listings, support. AllowedIntents: retry_pending_publication, publish_pending_listing. ReadOnly: false. RequiresConfirmation: true. RequiresChannel: true. Use when: The user asks to retry or resubmit an existing pending product after fixing a marketplace error, or explicitly asks to publish a pending product now. Use this action instead of telling the user to click Retry in HGRWeb. SearchTerms: retry pending listing, retry publishing, publish pending listing now, resubmit pending product, retry failed publication, retry ebay publication. NegativeUseCases: Do not retry automatically merely because the user asks what the error means; Do not use for relisting an active or terminated product. Input: [FromBody] rq: Request.ListNowRequest. Id is the first variation ID, not its parent ListingId. Resolve the attached product or GetPending listingId through Listing/GetListings with ListingIds and Projection=Identifiers in the selected channel, then use variations[0].id, as HGRWeb Retry does. Header channel: current ChannelOAuthId. Output: BaseResponse.Success reports whether the retry or scheduling request was accepted, not whether marketplace publication has completed. Search terms: searchproduct listnow. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/SearchProduct/ListNow request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_optimize ~248

Dedicated HGRApi tool for POST api/SearchProduct/Optimize. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST optimize operation in existing published product/listing management. Use when: Use it when a client needs to run the optimize operation for existing published product/listing management. Input: [FromBody] data: OptimizeRequest. Main fields: ListingId: int?, ProductSourceId: int?, CurrentTitle: string, OptimizeTitle: bool, OptimizeDescription: bool, OptimizeFields: bool. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the optimize operation. Search terms: searchproduct optimize. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/SearchProduct/Optimize request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_pausetoreview ~367

Dedicated HGRApi tool for POST api/SearchProduct/PauseToReview. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Moves a scheduled pending product to manual review so it is not published at its scheduled time. ReadOnly: false. RequiresConfirmation: true. RequiresChannel: true. Use when: The user asks to pause, hold or stop a scheduled pending product so it is reviewed before publication. SearchTerms: pause pending listing, move pending listing to review, hold scheduled publication, stop scheduled listing. NegativeUseCases: Do not use for active or terminated listings. Input: [FromBody] rq: Request.ListNowRequest. Id is the first variation ID, not its parent ListingId. Resolve the attached product or GetPending listingId through Listing/GetListings with ListingIds and Projection=Identifiers in the selected channel, then use variations[0].id, as HGRWeb Pause does. Header channel: current ChannelOAuthId. Output: BaseResponse.Success is true when the product moved to review. It is false when the variation belongs to another channel, the product is not scheduled for its first listing, or its scheduled time is less than 3 minutes away. Search terms: searchproduct pausetoreview. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/SearchProduct/PauseToReview request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_recoverlisting ~273

Dedicated HGRApi tool for POST api/SearchProduct/RecoverListing. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Recovers one hidden published product in the selected reconnected store. ownerAgent: listings. Domain: listings. Entity: recoverable_listing. Operation: recover_one. Scope: current_store. Use when: Use after the user explicitly confirms recovery of one product from getMissingListings.RecoverableListings. Input: Header channel: current ChannelOAuthId. Body ListingId is the exact HGR product ID returned in RecoverableListings, not a variation ID or marketplace PrimaryId. No import settings. Output: Returns RecoveredCount: one if recovered, zero if the product is no longer recoverable in this store. Search terms: searchproduct recoverlisting. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/SearchProduct/RecoverListing request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_recoverlistings ~234

Dedicated HGRApi tool for POST api/SearchProduct/RecoverListings. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Recovers all hidden published products in the selected reconnected store. ownerAgent: listings. Domain: listings. Entity: recoverable_listing. Operation: recover_all. Scope: current_store. Use when: Use after the user explicitly confirms recovery of products returned in getMissingListings.RecoverableListings. Input: Header channel: current ChannelOAuthId. No body or import options. Requires ownership of the linked store and user confirmation. Output: Returns RecoveredCount, the number of existing HGR products restored; repeated requests may return zero. Search terms: searchproduct recoverlistings. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_relist ~228

Dedicated HGRApi tool for POST api/SearchProduct/Relist. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST relist operation in existing published product/listing management. Use when: Use it when a client needs to run the relist operation for existing published product/listing management. Input: [FromBody] rq: RelistRequest. Main fields: Id: int. Header channel: current ChannelOAuthId. Output: Returns the result or applies the effect of the relist operation. Search terms: searchproduct relist. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/SearchProduct/Relist request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_removelisting ~384

Dedicated HGRApi tool for POST api/SearchProduct/RemoveListing. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Removes one listing from HGR. HGRWeb uses it to delete pending listings in review or error so they are never published. ReadOnly: false. RequiresConfirmation: true. RequiresChannel: true. Use when: The user explicitly asks to remove or delete a pending listing so it is never published. SearchTerms: remove pending listing, delete pending listing, remove listing from HGR. Input: [FromBody] rq: Request.ListNowRequest. Id is a variation ID of the listing to remove, not its parent ListingId. Resolve the attached product or GetPending listingId through Listing/GetListings with ListingIds and Projection=Identifiers in the selected channel, then use variations[0].id, as HGRWeb Remove does. The whole listing that owns that variation is removed. Header channel: current ChannelOAuthId, used to resolve the variation; the endpoint itself does not check it. Output: BaseResponse.Success is true when the listing was marked removed and false when no listing in the authenticated user's stores owns that variation ID. Search terms: searchproduct removelisting. Send the exact request payload in body. Requires confirmed=true and impactConfirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/SearchProduct/RemoveListing request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_savemultipleproductchanges ~502

Dedicated HGRApi tool for POST api/SearchProduct/SaveMultipleProductChanges. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST save multiple product changes operation in existing published product/listing management. Use when: Use it when a client needs to run the save multiple product changes operation for existing published product/listing management. Input: [FromBody] changes: SaveMultipleProductChangesRequest. Main fields: ListingIds: int[], DataByListing: Dictionary<int, SaveMultipleProductChangesRequestD>, Markup: SaveProductChangeNumber, IncreaseMarkup: SaveProductChangeNumber, Price: SaveProductChangeDecimal, Quantity: SaveProductChangeNumber, Profit: SaveProductChangeNumber, MonitorPrice: SaveProductChangeBoolean, MonitorStock: SaveProductChangeBoolean, MonitorPriceDecrease: SaveProductChangeBoolean, PriceDecreasePercentage: SaveProductChangeNumber, IgnoreRules: SaveProductChangeBoolean, MinQuantity: SaveProductChangeNumber, PrimeOnly: SaveProductChangeBoolean, ShippingPolicy: SaveProductChangeLong, ReturnPolicy: SaveProductChangeLong, PaymentPolicy: SaveProductChangeLong, DispatchTimeDays: SaveProductChangeNumber. Header channel: current ChannelOAuthId. VAT is optional and only supported for eBay API: omit to leave unchanged, use {value: integer} from 0 to 100 to set, or {value: null} to remove the override and send zero to eBay. VAT applies to every variation of the affected eBay listing. Output: Returns the result or applies the effect of the save multiple product changes operation. Side effect: when a new channel stock quantity is applied to a listing variation, its previous channel stock quantity is recorded in the stock history (author: user), so it appears in the stock changes history. VAT settings are saved only for provider-accepted changes. Search terms: searchproduct savemultipleproductchanges. Send the exact request payload in body. Requires confirmed…

NameTypeReqDescription
body–yesHGRApi POST /api/SearchProduct/SaveMultipleProductChanges request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_searchproduct_terminatelisting2 ~309

Dedicated HGRApi tool for POST api/SearchProduct/TerminateListing2. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the POST terminate listing2 operation in existing published product/listing management. Use when: Use it when a client needs to run the terminate listing2 operation for existing published product/listing management. Input: [FromBody] item: TerminateItemRequest. Main fields: Id: int. Header channel: current ChannelOAuthId. Output: Ends the listing in the store. Marks it terminated in HGR and returns success=true only when the store confirms the end or reports that the item was already ended. When the store refuses the end, returns success=false and the listing stays active in HGR. Search terms: terminatelisting 2, searchproduct terminatelisting 2. Send the exact request payload in body. Requires confirmed=true and impactConfirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST /api/SearchProduct/TerminateListing2 request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_smartlister_filters_checknew ~223

Dedicated HGRApi tool for POST ai publisher filters checknew. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Checks whether a proposed AI Publisher order returns enough current product candidates. ownerAgent: ai-publisher. Use when: Use to check candidate availability without saving an order or publishing products. Input: NewFiltersRequest. Filter.Criteria is the optional free-text product search prompt, not a literal title substring. Supplier, price, profit, Prime and tag filters apply. Header channel: current ChannelOAuthId. Output: Returns GOOD, INSUFFICIENT or BAD based on up to 50 search results. Search terms: ai publisher filters checknew. Send the exact request payload in body. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST ai publisher filters checknew request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_post_smartlister_filters_new ~366

Dedicated HGRApi tool for POST ai publisher filters new. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Creates a scheduled AI Publisher publication order for the selected store, including search conditions copied from the catalog. ownerAgent: ai-publisher. Use when: Use to create an order with product conditions, quantity, schedule and optimization preferences. Input: NewFiltersRequest.Filter: supplier Sources, OnlyPrime, optional Criteria (the free-text search prompt, up to 4000 characters; not a literal title substring), PriceMin/PriceMax, ProfitMin/ProfitMax and optional Tags (array of separate integer IDs, not bit flags). Tag IDs: 1 Valentine's Day, 2 Mother's Day, 3 Father's Day, 4 Back to school, 5 Halloween, 6 Black Friday, 7 Cyber Monday, 8 Christmas, 9 New Year's Eve, 10 Prime Day, 11 Trending, 12 Home and garden, 13 Electronics, 14 Toys and games, 15 Health and beauty, 16 Sports, 17 Pet supplies. Header channel: current ChannelOAuthId; the selected store determines ChannelOauthId. Output: Returns the identifier of the created order. Search terms: ai publisher filters new. Send the exact request payload in body. Requires confirmed=true before execution. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
body–yesHGRApi POST ai publisher filters new request body.
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_process_order_lines ~93

Starts normal processing for orders resolved from visible order Reference. Requires confirmed=true. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
referencestring–Visible marketplace/order reference.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_refresh_business_policies ~82

Refreshes marketplace business policies for one visible store. Requires confirmed=true. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.

Structured output declared, but exposes no named fields.

No examples provided.

hgr_relist_listing ~158

Relists one terminated listing by visible Product ID. Requires confirmed=true and impactConfirmed=true after warning about consequences. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

NameTypeReqDescription
channelOAuthIdintegeryesChannelOAuthId returned by hgr_list_channels for the selected visible store.
confirmedbooleanyesMust be true after the user explicitly requested or confirmed the exact action.
impactConfirmedbooleanyesMust be true after the user explicitly confirmed the concrete high-impact consequences.
pendingListingIdinteger–Visible pending listing id, only for pending listings where HGRWeb shows this id.
productIdstring–Visible marketplace Product Id / primary id. Prefer this for active or terminated listings.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Hustle Got Real MCP server?

Hustle Got Real is a hosted endpoint at https://mcp.hustlegotreal.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.hustlegotreal.com

# add to Claude Code
claude mcp add --transport http com-hustlegotreal-mcp 'https://mcp.hustlegotreal.com/'
Common questions

What is the Hustle Got Real MCP server?

Hustle Got Real is an MCP server listed in the public MCP registry as com.hustlegotreal/mcp. Dropshipping for eBay, Amazon and Shopify: products, listings, prices, stock, orders and analytics. This page covers its hosted endpoint (https://mcp.hustlegotreal.com/).

Is the Hustle Got Real MCP server safe to use?

Hustle Got Real scores 57 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Hustle Got Real MCP server expose?

Hustle Got Real exposes 172 tools: hgr_get_authenticated_user, hgr_list_channels, hgr_get_subscription_summary, hgr_get_active_listings, hgr_get_pending_listings, and 167 more. Their descriptions and schemas cost roughly 31,732 tokens of context every time the server is loaded.

Does the Hustle Got Real MCP server require authentication?

No. We connected to Hustle Got Real without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Hustle Got Real MCP server still maintained?

Hustle Got Real is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Hustle Got Real MCP server?

VerifyMCP ran 13 checks on Hustle Got Real, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.