Skip to main content
Glama

Changes to products and prices

get_product_changes
Read-onlyIdempotent

Use this for what changed: with a slug, the timeline of one product; without, the feed across the catalog since a date, filtered by change type (price_drop, new_integration, ...) or category. A research_update is a change to OUR knowledge (unknown, estimated), never to the product.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_product_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoA product slug for its own timeline. Omit for the catalog-wide feed.
limitNo
sinceNoFeed only: earliest day, YYYY-MM-DD.
typesNoFeed only: change types to include. Known: price_drop, price_increase, new_price, new_product, new_ai_agent, new_integration, new_alternative, security_certification, product_change, documented, research_update, funding, acquisition, source_changed.
categoryNoFeed only: a category slug.
statement_idNoFeed only: the stable statement id from a product attribute. Includes corrections and withdrawals.
include_minorNoInclude changes that are not material.

Output Schema

NameRequiredDescriptionDefault
slugNo
countYes
sinceNo
typesNo
changesYes
web_urlYes
contractYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious semantics that annotations cannot convey: a research_update is a change to the provider's own knowledge (values may be unknown or estimated) and is never a change to the product itself. That warning materially affects interpretation of results. Return shape and pagination are left to the output schema, which is reasonable.

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 sentences, no filler, with the usage trigger front-loaded and the mode distinction immediately after. The parenthetical enum examples and the closing research_update caveat each carry real information rather than restating the schema.

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?

Seven optional parameters across two working modes plus a nuanced change-type taxonomy is a lot to cover, and the description handles the mode split and the trickiest type correctly. Return values need not be explained because an output schema exists. It falls short of complete only in not touching include_minor, which changes whether non-material changes appear and is arguably a meaningful behavioral choice.

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 86%, so the baseline is 3 and the schema already documents slug, since, types, category and statement_id. The description still earns above baseline by explaining the mutual exclusivity of the slug timeline vs the feed, and by defining what the research_update enum member actually means. It does not clarify include_minor or limit, which remain schema-only.

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?

The description opens with a specific verb phrase ('Use this for what changed') and then spells out two distinct retrieval modes: a single product timeline when a slug is given, and a catalog-wide feed otherwise. It is clearly distinguishable from a current-state tool like get_product by framing everything as change history. It does not explicitly name a sibling, which keeps it short of a 5.

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 states positively when to reach for this tool ('for what changed') and gives the condition that selects each mode (slug present vs absent), plus the available feed filters. What is missing is an explicit 'use X instead when...' exclusion against siblings such as get_product or get_statement, so it stops at 4.

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