Skip to main content
Glama

Post Channellisting Monitorexistinglisting2

hgr_post_channellisting_monitorexistinglisting2
Destructive

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. Optional PricingMode: 0 (default) applies normal markup; 1 preserves the store sale price until usable supplier cost is available, then calculates and saves individual markup once. While waiting, supplier out-of-stock sets quantity to zero without changing the sale price. Reactivated terminated products use the same selected mode. Selecting default markup clears an unresolved store-price initialization from an earlier attempt. Unknown modes are rejected. 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.

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

Input Schema

NameRequiredDescriptionDefault
bodyYesHGRApi POST /api/ChannelListing/MonitorExistingListing2 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.7/5.0
Behavior5/5

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

Annotations already flag destructive and non-idempotent, but the description adds substantially more: SSE streaming behavior, 'Authenticated, not admin-only', the precedence rule that the Header channel/ChannelOAuthId wins over a body OAuthId, PricingMode side effects (mode 1 preserves store sale price until supplier cost exists, out-of-stock zeroes quantity without changing price, switching to default clears an unresolved initialization), unknown modes rejected, ToRelist ignored, and UserDevice to be omitted by AI/MCP. It also warns that a terminal completed event does not mean all products were imported, which is exactly the kind of result-interpretation guidance annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is long, but this is a streaming destructive mutation with a nested body, so most sentences earn their place, and the Purpose / Use when / Input / Output ordering is easy to scan. The lead sentence ('Dedicated HGRApi tool for POST ...; it is not a generic endpoint caller') and the trailing 'Search terms' line are filler that could be cut without losing information.

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

Completeness5/5

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

For a tool with auth, a nested body, a pricing-mode branch, streaming output and a confirmed flag, the description covers every decision an agent must make before calling: eligibility, payload shape, header precedence, confirmation, and how to judge the result. An output schema exists, yet the description's warning about interpreting ok/failed/processed versus total is still functionally necessary rather than redundant.

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

Parameters5/5

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

Schema coverage is already 100%, so the baseline would be 3, but the description adds real meaning: the body is an AddListingModel whose Listings carry Id, SourceURL and optional VariationSku/VariationAttributes/SourceVariation/SourceWarehouse/Markup/Title, PricingMode enumerates 0 vs 1 with consequences, and it disambiguates the channelOAuthId parameter by stating the body OAuthId does not override the header.

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?

Beyond restating the endpoint, it states the actual function: 'Imports existing store products into HGR with live progress over one HTTP stream' and clarifies 'Imported products are activated; no new marketplace adverts are published.' That scope sentence separates it from publication-oriented siblings such as hgr_post_ai_publishnow and hgr_post_listing_autolist, and from catalog discovery tools.

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

Usage Guidelines4/5

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

It gives an explicit precondition set for use ('exact existing store product ids and supplier URLs are selected and the caller can keep an SSE response open'), an instruction to send the entire selection in one request, and an explicit exclusion ('Do not use for catalog discovery or new marketplace publication'). The one gap is that it never names or routes to the near-duplicate sibling hgr_post_channellisting_monitorexistinglisting, so an agent must infer the version distinction.

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