Skip to main content
Glama

Post Searchproduct Listnow

hgr_post_searchproduct_listnow
Destructive

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.

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>",
      "confirmed": "<confirmed>",
      "channelOAuthId": "<channelOAuthId>"
    },
    "name": "hgr_post_searchproduct_listnow"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesHGRApi POST /api/SearchProduct/ListNow request body.
confirmedYesMust be true after the user explicitly requested or confirmed the exact action.
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.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description still adds non-obvious behavior: RequiresConfirmation=true, RequiresChannel=true, a specific prerequisite resolution path (Listing/GetListings with Projection=Identifiers, then variations[0].id), and the key caveat that Success means the request was accepted, not that marketplace publication completed. It partially restates structured metadata ('ReadOnly: false'), which earns no credit.

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 operative guidance is front-loaded and the negative cases are clearly separated, but the definition is bloated with scaffolding ('Dedicated HGRApi tool for POST api/...', 'it is not a generic endpoint caller', a duplicate 'Search terms: searchproduct listnow', and metadata lines that restate annotations). Several sentences do not earn their place.

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?

For a destructive, confirmation-gated mutation, the description covers prerequisites, channel resolution, confirmation, output semantics and exclusions. The remaining gap is the body payload: it is given as a bare request type (Request.ListNowRequest) with no field documentation, so the agent must infer required body contents.

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 explains confirmed and channelOAuthId, so baseline 3 applies. The description goes beyond it by disambiguating the body: 'Id is the first variation ID, not its parent ListingId,' plus the resolution procedure to obtain it. It stops short of enumerating body fields, which are undocumented in both schema and description.

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 object: 'Retries a failed pending publication or submits a pending product now.' The functional header (Domain: listings, Entity: pending_listing, Operation: retry_or_publish) pins the scope, and the explicit contrast with relisting ('Do not use for relisting an active or terminated product') separates it from siblings like hgr_post_searchproduct_relist and hgr_relist_listing.

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?

Contains an explicit 'Use when:' clause and an explicit 'NegativeUseCases:' clause, including the subtle exclusion 'Do not retry automatically merely because the user asks what the error means.' It even routes the agent away from manual workarounds ('instead of telling the user to click Retry in HGRWeb').

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