Skip to main content
Glama

sonar

by app.trysonar
OverviewDiscussionsAdmin

Fetch App Reviews

sonar_app_reviews
Read-onlyIdempotent

Fetch user reviews for any app, live from the store (up to ~500 of the most recent or most helpful for the country). The star-rating filters and limit apply to that fetched window, so a narrow filter on a small app can return few or no reviews. Useful for sentiment analysis, feature-request mining, and competitive research; for an already-summarized view of a tracked app, sonar_review_insights returns themed AI analysis instead. Needs a Sonar API key or connected account (1 credit per call on prepaid API credits); not part of the free tier. If the store is throttling, the result may be Sonar's stored copy: it then comes back as { data, meta } with meta.stale: true, its date in meta.stale_as_of, and a meta.note to pass on to the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoAndroid only: fetch one language feed (e.g. ar, fr). Omit to merge the market language plus en, es, fr, ar; coverage is not exhaustive.
sortNoSort order. "recent" returns newest first, "helpful" returns most-voted first.recent
limitNoMaximum number of reviews to return (1-200).
storeYesApp store. "ios" for Apple App Store, "android" for Google Play.
countryNoMarket as an ISO 3166-1 alpha-2 code (e.g. "us", "gb", "de", "mt"). Any App Store storefront (175 countries) or Google Play market (145). Default "us".us
store_idYesStore-specific app identifier. iOS: bundle ID or numeric track ID — the `storeId` returned by sonar_app_search works as-is. Android: package name.
max_ratingNoFilter to reviews with a star rating <= this value (1-5).
min_ratingNoFilter to reviews with a star rating >= this value (1-5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / store_id / description
      Previous value: -"Store-specific app identifier. iOS: numeric track ID. Android: package name."New value: +"Store-specific app identifier. iOS: bundle ID or numeric track ID — the `storeId` returned by sonar_app_search works as-is. Android: package name."
  2. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-2 country code (e.g. \"us\", \"gb\", \"de\"). Default \"us\"."New value: +"Market as an ISO 3166-1 alpha-2 code (e.g. \"us\", \"gb\", \"de\", \"mt\"). Any App Store storefront (175 countries) or Google Play market (145). Default \"us\"."
  3. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
+  "description": "Android only: fetch one language feed (e.g. ar, fr). Omit to merge the market language plus en, es, fr, ar; coverage is not exhaustive.",
+  "pattern": "^[a-z]{2}$",
+  "type": "string"
+}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial context beyond them: API-key/connected-account requirement, cost (1 credit per call, not free tier), and the throttling fallback behavior with the exact `{ data, meta }` shape, `meta.stale`, `meta.stale_as_of`, and `meta.note` to relay to the user.

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?

Purpose is front-loaded and the four sentences are dense with distinct value (routing, filters-vs-window caveat, cost/auth, stale fallback). It is on the longer side and the throttling detail is information-heavy, but each sentence carries unique information rather than padding.

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 read-only tool with no output schema, the description covers the missing pieces an agent needs: auth/cost prerequisites, the sparse-filter caveat, and the alternate return shape under throttling. Nothing needed to call it correctly appears to be absent.

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, but the description adds meaning beyond the schema by explaining that the star-rating filters and `limit` operate on the fetched window (up to ~500), which explains why filtered results can be sparse. It doesn't restate per-parameter syntax, appropriately leaving that to the schema.

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 user reviews for any app") plus the source ("live from the store") and scope (~500 most recent or helpful per country). It explicitly distinguishes itself from the sibling sonar_review_insights, which returns themed AI analysis, so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

Gives concrete when-to-use contexts (sentiment analysis, feature-request mining, competitive research) and names the alternative for summarized data (sonar_review_insights). It also warns about a usage pitfall: a narrow filter on a small app may return few or no reviews, since filters apply to the fetched window.

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

All sonar toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources