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

Name	Required	Description
`to`	No	comparison date YYYY-MM-DD (optional, default newest)
`from`	No	baseline date YYYY-MM-DD (optional)
`appId`	Yes	App Store or Google Play URL, iOS / Mac App Store numeric id (e.g. 324684580) or Android package (e.g. com.spotify.music) — get ids from search_apps
`store`	No	optional — inferred from appId (numeric id / App Store URL → ios, package / Play URL → android); iOS and Mac App Store share the same URL shape, so pass "macos" explicitly for Mac apps

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026

changedInput schema / properties / appId / description

Previous value: -"App Store or Google Play URL, iOS numeric id (e.g. 324684580) or Android package (e.g. com.spotify.music) — get ids from search_apps"New value: +"App Store or Google Play URL, iOS / Mac App Store numeric id (e.g. 324684580) or Android package (e.g. com.spotify.music) — get ids from search_apps"

changedInput schema / properties / store / description

Previous value: -"optional — inferred from appId (numeric id / App Store URL → ios, package / Play URL → android)"New value: +"optional — inferred from appId (numeric id / App Store URL → ios, package / Play URL → android); iOS and Mac App Store share the same URL shape, so pass \"macos\" explicitly for Mac apps"

changedInput schema / properties / store / enum

Previous value: -[
-  "ios",
-  "android"
-]New value: +[
+  "ios",
+  "macos",
+  "android"
+]

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real behavioral context on top: 'Instant (archive read, no LLM)' discloses cost/latency characteristics, the default comparison window is stated, and the degenerate case ('Returns a note when the app has fewer than two snapshots yet') tells the agent how failure manifests rather than throwing an error.

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?

Five compact clauses, front-loaded with what the tool returns, followed by cost, defaults, and the edge case in descending order of importance. No sentence is redundant with the name or title.

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?

There is no output schema, so the description carries the return contract — and it does: label taxonomy, delta unit (percentage points), and the low-snapshot note. Combined with the 100%-covered input schema, an agent has everything needed to call it and interpret the result.

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; the description exceeds it by supplying a default for `from` (approximately 30 days earlier) that the schema does not state, and by framing `from`/`to` as baseline/comparison rather than leaving their roles implicit. It does not add syntax detail beyond what the enum and format strings already give.

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?

Specific verb and resource: 'compares two archived analyses and labels each theme new / resolved / rising / falling / stable with share deltas'. The output vocabulary is named, so an agent knows exactly what it gets and can distinguish it from mine_app_pain_points (which produces the analyses) and get_version_history.

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?

Implies the prerequisite condition clearly — it reads archived analyses, so snapshots must already exist — and states the default window (latest vs ~30 days earlier). What it does not do is explicitly name the sibling to call first (mine_app_pain_points) or a when-not-to-use case, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All App Pain API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.