Skip to main content
Glama

App Pain API

Raw reviews

get_app_reviews
Read-onlyIdempotent

Fetch raw app reviews (unified schema across stores: rating/title/body/version/date/devReply/thumbsUp), 50 per page. Use for drill-down after mine_app_pain_points.

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

Input Schema

NameRequiredDescriptionDefault
pageNopage number, default 1 (50/page)
sortNodefault recent (Android: both supported; iOS/macOS use the store default order)
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

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/openWorld, so the safety profile needs no restating. The description earns credit for disclosing that the output is *raw* and unfiltered with a fixed 50-per-page shape, which matters with no output schema, though it omits the 10-page cap that constrains how deep a drill-down can go and leaves the Steam reviews limitation to the schema.

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?

Two tight clauses with the payload description front-loaded and the drill-down guidance second, no filler. The parenthetical field list is dense but earns its place because there is no output 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?

For a paging read tool with no output schema, the description covers what a caller needs: what records come back in what shape, how many per call, and where it sits in the analysis workflow. Remaining details (max page, Steam unavailability) are already carried by the schema descriptions.

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 schema itself documents page numbering, sort enum behavior per store, store inference rules, and country default. The description only echoes '50 per page', so it adds essentially nothing beyond what the structured field already provides; baseline 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 specific verb and resource ('Fetch raw app reviews') and immediately scopes the payload by enumerating the unified fields returned (rating/title/body/version/date/devReply/thumbsUp) plus page size. It is clearly distinguishable from mine_app_pain_points, which is the aggregated counterpart it points back to.

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?

'Use for drill-down after mine_app_pain_points' gives an explicit trigger and names the sibling that precedes it, which is real routing guidance. It stops short of stating when not to use it (e.g. when summary-level data from get_app_details or get_pain_trend suffices).

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.