Skip to main content
Glama

App Pain API

Mine app pain points

mine_app_pain_points
Read-onlyIdempotent

THE core tool: fetch recent reviews of any iOS/Android app, keep the negative ones, and cluster them into ranked pain points (title, sharePercent, severity 1-5, verbatim evidence quotes). Ideal for competitive research and product discovery. Cached 7 days (instant on repeat); a COLD server-side analysis takes 30-120s. If the result has "mode":"agent", it contains prepared negative reviews and "instructions" — do the clustering yourself and present it to the user. Not available for Steam (mine the game's mobile counterpart instead).

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": "mine_app_pain_points"
  }
}

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
modelNopremium refinement model (paid keys only). Omit for the free default.
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
analyzeNowho clusters on a cold run: "server" = our model; "agent" = you get the prepared negative reviews + instructions and cluster them with your own model; "auto" (default) = server, switching to agent when the server-side allowance is used up
countryNoISO country code, default "us"
reviewsNoreviews to analyze, default 300 (other values round up to these tiers; Apple rate limiting can occasionally cap depth below the target)
maxRatingNoratings <= this count as negative, default 3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, and the description layers on real operational context the annotations cannot convey: 7-day caching, a 30-120s cold server-side analysis, and an "agent" mode where the tool returns prepared negative reviews plus instructions and the caller must do the clustering. The Steam unavailability warning is also a genuine capability constraint.

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-loads the core purpose and output shape, then layers latency, cache, agent-mode, and store-availability caveats in separate clauses. Dense but every sentence carries actionable information; the heavy use of parentheticals and quotes makes it slightly harder to scan than it could be.

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?

For a 7-parameter tool with no output schema, the description compensates by naming the returned fields, disclosing latency and caching, and explaining the conditional agent-mode contract the caller must honor. Nothing essential to invoking it correctly or handling the response is missing.

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 description coverage is 100% and the parameter docs are already thorough (appId formats, store inference, analyze modes, review tiers). The description reinforces the negative-review threshold and analyze-mode behavior but adds no syntax or format detail beyond what the schema already states, so the baseline of 3 applies.

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 concrete pipeline of verbs (fetch reviews → keep negatives → cluster into ranked pain points) and even names the output fields (title, sharePercent, severity 1-5, verbatim quotes). This is clearly distinguishable from siblings like get_app_reviews (raw reviews) and get_pain_trend (trends) without opening any schema.

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 positive context ("THE core tool", ideal for competitive research and product discovery) and an explicit exclusion: Steam is not supported, mine the game's mobile counterpart instead. It also routes id lookup to search_apps via the schema. It does not explicitly contrast with get_app_reviews or explain when to prefer this over the raw-review sibling, which keeps it below a 5.

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.