Skip to main content
Glama

Get Listing Stock History

hgr_get_listing_stock_history
Read-onlyIdempotent

Reads stock history for one exact listing variation. 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": {
      "channelOAuthId": "<channelOAuthId>"
    },
    "name": "hgr_get_listing_stock_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdNoVisible marketplace Product Id / primary id.
channelOAuthIdYesChannelOAuthId returned by hgr_list_channels for the selected visible store.
variationProductIdNoVisible variation Product Id / primary id when the listing has multiple variations.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value by flagging that the channel is resolved internally and that ChannelOAuthId must come from hgr_list_channels, but the phrasing 'Requires HGRApi Header channel / ChannelOAuthId resolved internally' is ambiguous about whether the caller must supply a header, and nothing is said about history depth or ordering.

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?

Two short sentences with the scope statement front-loaded and no filler. The second sentence, however, is dense and reads like a compressed internal note rather than clean prose, costing a point.

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?

An output schema exists so return values need not be described, and annotations cover the safety profile, which keeps the bar modest. Still, for a history-read tool the description never says what the history contains or over what window, and the header/channel sentence is too vague to fully resolve the one required parameter's provenance.

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% and the schema already explains productId, variationProductId and channelOAuthId, so the baseline applies. The description's phrase 'one exact listing variation' hints that variationProductId identifies the variation, but it adds no format, default, or mutual-exclusion guidance beyond the schema.

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

Purpose4/5

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

States a specific verb and resource ('Reads stock history') and narrows scope to 'one exact listing variation', which distinguishes it from the listing-level siblings like hgr_get_active_listings or hgr_get_listings. It does not, however, distinguish it from the closest sibling hgr_get_listing_price_history, whose name follows the identical pattern.

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?

There is no stated condition for when to call this versus alternatives, and the obvious near-alternative (hgr_get_listing_price_history) is never mentioned. The only usage-like content is a prerequisite ('Requires HGRApi Header channel / ChannelOAuthId'), not a when-to-use rule.

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