Skip to main content
Glama

App Pain API

Version history

get_version_history
Read-onlyIdempotent

Per-version review stats (review count, average rating, first/last seen) — spot a rating crash right after a bad release. Android: aggregated from recent reviews. iOS: current version + release notes. Steam: not available (Steam exposes no per-version data — returns an empty list).

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": {
      "appId": "<appId>"
    },
    "name": "get_version_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesApp Store / Google Play / Steam / WordPress.org / Chrome Web Store URL, iOS / Mac App Store numeric id (e.g. 324684580), Android package (e.g. com.spotify.music), Steam appid (e.g. 730), WordPress plugin slug (e.g. woocommerce) or Chrome extension id — get ids from search_apps
storeNooptional — inferred from appId (App Store URL or 5-12 digit id → ios, Play URL / package → android, Steam URL or 1-4 digit appid → steam); iOS and Mac App Store share the same URL shape, so pass "macos" explicitly for Mac apps. steam: details/search only for now — mining/reviews return steam_reviews_unavailable
countryNoISO country code, default "us"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive, so the bar is lower, and the description still adds real behavioral context: Android figures are aggregates of recent reviews, iOS returns only the current version plus release notes, and Steam returns an empty list. It omits any note on result size or pagination, which keeps it off a 5.

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?

Front-loaded with what is returned before the per-platform qualifications, and every clause (Android aggregation, iOS scope, Steam unavailability) earns its place. The em-dash platform chain is dense but readable; no filler sentences.

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 enumerates the returned fields and flags that iOS yields no genuine version history and Steam yields nothing at all — the details an agent needs to avoid misinterpreting results. Minor gaps remain around result volume and whether Android aggregation is time-boxed.

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 coverage is 100%, including enum values and inference rules, so the schema carries parameter meaning almost entirely. The description contributes nothing about appId, store or country semantics, leaving this at the baseline for fully documented schemas.

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 resource and scope: per-version review stats with the exact fields returned (review count, average rating, first/last seen). It clearly is not the raw review feed, but it never names get_app_reviews as the alternative, so sibling differentiation is implied rather than stated.

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 phrase 'spot a rating crash right after a bad release' supplies a concrete use case, and the Steam note tells the agent when the call is pointless. However, there is no explicit when-to-use-this-vs-get_app_reviews guidance or stated preconditions (e.g. that an appId must first come from search_apps).

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.