Skip to main content
Glama

App Pain API

Pain-point trend

get_pain_trend
Read-onlyIdempotent

How an app's pain points changed over time: compares two archived analyses and labels each theme new / resolved / rising / falling / stable with share deltas (percentage points). Instant (archive read, no LLM). Default: latest vs ~30 days earlier. Returns a note when the app has fewer than two snapshots yet.

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

Input Schema

NameRequiredDescriptionDefault
toNocomparison date YYYY-MM-DD (optional, default newest)
fromNobaseline date YYYY-MM-DD (optional)
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description adds real context beyond them: an instant, no-LLM archive read, the default comparison window, and the explicit edge-case behavior when fewer than two snapshots exist. It stops short of describing cost or rate limits, but for a cheap read there is little more to disclose.

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?

Three tight sentences, front-loaded with what the tool computes and its output vocabulary, then performance characteristics, then the default and edge case. No redundant or ornamental wording.

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?

With no output schema present, the description carries the burden of defining return values, and it does: trend labels per theme, percentage-point deltas, and a note when there are fewer than two snapshots. Combined with 100% schema coverage, an agent has everything needed to call it correctly.

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 100%, so the baseline is 3, but the description adds the missing default for the 'from' parameter (~30 days earlier) that the schema leaves unspecified, and frames 'from'/'to' as baseline vs comparison dates. App-level semantics (appId formats, store inference) are already fully documented in the schema.

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+resource (compares two archived analyses to produce a pain-point trend) and enumerates the exact output categories: new / resolved / rising / falling / stable with share deltas in percentage points. The word 'archived' implicitly separates it from mine_app_pain_points, which produces the underlying analyses.

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?

Gives clear operating context — it reads archived analyses rather than running an LLM pass, so it is instant, and the default window is latest vs ~30 days earlier. It does not explicitly name when to prefer it over mine_app_pain_points or state the prerequisite that snapshots must first exist, though the two-snapshot note hints at it.

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.