Skip to main content
Glama

Post Searchproduct Relist

hgr_post_searchproduct_relist
Destructive

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.

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_relist"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesHGRApi POST /api/SearchProduct/Relist 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

C2.8/5.0
Behavior3/5

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

The description adds the useful requirement that confirmed=true must be set before execution and that the header channel is resolved internally. However, for a destructive, non-idempotent operation, it does not explain what relisting actually changes, whether it creates a new listing, affects fees, or has other side effects.

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 description is front-loaded with the endpoint and confirmation requirement, but it contains significant boilerplate ('Dedicated HGRApi tool,' 'explicit tool with a fixed endpoint,' 'functional documentation,' 'Search terms') that does not help an agent invoke the tool correctly.

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

Completeness3/5

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

The description provides the endpoint, required confirmation, and channel header context, and an output schema exists so return values need not be described. Still, it leaves important gaps about the relist effect and how this tool differs from sibling relist operations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds some information about the body containing a RelistRequest with 'Main fields: Id: int,' but this is minimal and leaves most of the request body structure unexplained.

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

Purpose3/5

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

The description names a specific endpoint (POST api/SearchProduct/Relist) and says it is for 'existing published product/listing management,' but the actual purpose is still largely circular: 'relist operation' restates the tool name without explaining what relisting does. It does not differentiate this tool from siblings such as hgr_relist_listing or hgr_post_listing_relistedbulk2.

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

Usage Guidelines2/5

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

The only usage guidance is 'Use it when a client needs to run the relist operation,' which is tautological. It gives no when-not-to-use criteria and names no alternative tools for relisting, despite several relist-related siblings existing.

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