Skip to main content
Glama

Get daily price history of a tracked product

get_product_price_history
Read-onlyIdempotent

Returns one entry per day for a tracked product over the requested window (1 to 90 days, 30 by default): rank, gap to the best price, offer count and the offers that changed that day. Days beyond the plan retention come back locked. Optional channelId restricts to one marketplace.

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": {
      "productId": "<productId>"
    },
    "name": "get_product_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
channelIdNo
productIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description still adds real behavior the annotations cannot: days beyond plan retention come back locked, which warns the agent that results may be partially gated rather than empty or erroneous. Return-field enumeration further reduces surprise.

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

Conciseness5/5

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

Two dense sentences with the scope/return content front-loaded and the window constraint plus retention caveat following. No filler wording, every clause carries information an agent would otherwise have to guess.

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?

With no output schema, the description correctly compensates by listing the returned fields and the locked-day behavior. It is nearly complete for a read-only history query; only what happens on an untracked or invalid productId is left unstated.

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 description coverage is 0%, so the description carries the burden and largely does: it supplies the days range and default, and explains channelId as restricting to one marketplace. productId is only implied by 'tracked product' and no format or failure semantics are given, leaving a small gap.

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 resource ('Returns one entry per day for a tracked product') with the granularity and window made explicit, and enumerates the payload (rank, gap to best price, offer count, changed offers). That daily-history framing distinguishes it cleanly from offer-listing or current-position siblings without needing to name them.

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

Usage Guidelines3/5

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

The description gives concrete operating context (1-90 day window, 30-day default, optional channelId narrowing) but never says when to reach for this tool versus get_product_offers or list_price_positions. Usage is implied by the tool's nature rather than guided.

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.