Skip to main content
Glama

App Pain API

App details

get_app_details
Read-onlyIdempotent

App metadata: name, developer, category, price, average rating, rating count and 1-5★ histogram (when available).

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

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description contributes one genuine behavioral detail — that the rating histogram may be absent — but says nothing about what happens for an unknown or unavailable app, or about store inference edge cases.

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?

A single tight sentence that front-loads the resource and then lists the returned fields; every clause carries information and there is no filler.

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 simple read-only lookup with no output schema, the field enumeration is exactly what an agent needs to know what comes back, and annotations plus a fully documented schema cover the rest. The only gap is the absence of any error/not-found behavior for an unresolvable id.

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 appId/store/country descriptions are unusually detailed (accepted id formats, inference rules, macOS override). The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

The description enumerates exactly what the tool returns — name, developer, category, price, rating, rating count, and a star histogram — which makes the retrieval purpose unambiguous. It never explicitly contrasts itself with siblings such as get_app_reviews or mine_app_pain_points, but the 'metadata' framing is naturally distinct from those.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not guidance: nothing tells the agent to call this before mining pain points, or to use search_apps first to resolve an id (that hint lives only in the schema). The only conditional is the parenthetical '(when available)', which is about data completeness, not tool selection.

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.