Skip to main content
Glama
storelift-mcp

storelift-mcp

Country prices

get_country_prices
Read-onlyIdempotent

Retrieve per-country app prices from App Store Connect and Google Play, compare each against rival medians, and get a suggested rounded price for local pricing decisions.

Instructions

Country prices for one of the app's products, read from App Store Connect / Google Play: per country the local price, its USD value and index (US = 100), whether it is still Apple's (or Google's) automatic price, the median of rivals that localize their prices (multiplier against Apple's automatic price, with how many rivals) and the difference in percent, plus a suggested price rounded to an attractive price point with its reason (rival median or income band). Rivals are the app's manual iOS rivals; a country needs at least 3 of them to be compared. summary counts countries priced above and below rivals and still on the automatic price. state is not_connected, pending (the first read is not done yet), permission (the key's role can't read prices), no_products or ok. products lists the other products; pass product to switch.

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

Input Schema

NameRequiredDescriptionDefault
appIdYesapp id from list_apps
countryNotwo-letter country code to return one row
productNoproduct id or SKU (defaults to the first product)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them. It enumerates the full state machine (not_connected, pending, permission, no_products, ok), which is essential for interpreting an empty or partial response, and explains what summary counts and what makes a country comparable (at least 3 manual iOS rivals).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with purpose, which is good, but the body is a single dense block of sentences with stacked parentheticals ('and index (US = 100)', 'with how many rivals'). Nearly every clause carries real information, yet the lack of any structural separation makes the return-value and state details hard to scan.

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?

With no output schema, the description correctly takes on the burden of explaining the returned shape: per-country fields, a suggested price with its rationale, a summary block, a products list, and the state enum. That is thorough for a 3-parameter tool; only minor gaps remain, such as how large result sets are bounded or what is returned for a product with no rivals at all.

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 coverage is 100% and the schema already documents appId's provenance, country as a two-letter code, and product's SKU/default behavior. The description confirms those semantics ('country ... to return one row', product defaulting to the first product) but adds no new format or validation detail, so the baseline 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 opening clause names a precise resource and its source systems: 'Country prices for one of the app's products, read from App Store Connect / Google Play'. An agent immediately knows this returns localized pricing, not offers, revenue, or rival market data. It does not explicitly distinguish itself from the similar-sounding sibling get_pricing_offers, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'pass product to switch' and the country parameter 'to return one row' tell the agent how to narrow results, but there is no explicit when-to-use-this-vs-get_pricing_offers guidance, no prerequisite call ordering (beyond appId coming from list_apps in the schema), and no exclusions.

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