Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

app-store-reviews

Retrieve user reviews from the App Store to analyze feedback, track ratings, and understand customer sentiment for mobile applications.

Instructions

Get reviews for an App Store app. Returns an array of reviews with:

  • id: Review ID

  • userName: Reviewer's name

  • userUrl: Reviewer's profile URL

  • version: App version reviewed

  • score: Rating (1-5)

  • title: Review title

  • text: Review content

  • url: Review URL

  • updated: Review date (ISO string)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNumeric App ID (e.g., 553834731). Either this or appId must be provided.
appIdNoBundle ID (e.g., 'com.midasplayer.apps.candycrushsaga'). Either this or id must be provided.
countryNoCountry code to get reviews from (default: us)us
pageNoPage number to retrieve (default: 1, max: 10)
sortNoSort order (recent or helpful)recent

Implementation Reference

  • src/server.js:120-148 (registration)
    Registration of the 'app-store-reviews' tool using server.tool(), including description, input schema, and inline handler function.
    server.tool("app-store-reviews", 
      "Get reviews for an App Store app. Returns an array of reviews with:\n" +
      "- id: Review ID\n" +
      "- userName: Reviewer's name\n" +
      "- userUrl: Reviewer's profile URL\n" +
      "- version: App version reviewed\n" +
      "- score: Rating (1-5)\n" +
      "- title: Review title\n" +
      "- text: Review content\n" +
      "- url: Review URL\n" +
      "- updated: Review date (ISO string)",
      {
        id: z.number().optional().describe("Numeric App ID (e.g., 553834731). Either this or appId must be provided."),
        appId: z.string().optional().describe("Bundle ID (e.g., 'com.midasplayer.apps.candycrushsaga'). Either this or id must be provided."),
        country: z.string().default("us").describe("Country code to get reviews from (default: us)"),
        page: z.number().min(1).max(10).default(1).describe("Page number to retrieve (default: 1, max: 10)"),
        sort: z.enum(["recent", "helpful"]).default("recent").describe("Sort order (recent or helpful)")
      }, 
      async ({ id, appId, country, page, sort }) => {
        const reviews = await store.reviews({
          id,
          appId, 
          country,
          page,
          sort: sort === "helpful" ? store.sort.HELPFUL : store.sort.RECENT
        });
        return { content: [{ type: "text", text: JSON.stringify(reviews) }] };
      }
    );
  • Handler function that fetches reviews using the external 'store.reviews' method from '@jeromyfu/app-store-scraper' library, processes sort option, and returns JSON stringified reviews wrapped in MCP content format.
    async ({ id, appId, country, page, sort }) => {
      const reviews = await store.reviews({
        id,
        appId, 
        country,
        page,
        sort: sort === "helpful" ? store.sort.HELPFUL : store.sort.RECENT
      });
      return { content: [{ type: "text", text: JSON.stringify(reviews) }] };
    }
  • Zod input schema defining parameters for the tool: app ID or bundle ID, country, page, and sort order.
    {
      id: z.number().optional().describe("Numeric App ID (e.g., 553834731). Either this or appId must be provided."),
      appId: z.string().optional().describe("Bundle ID (e.g., 'com.midasplayer.apps.candycrushsaga'). Either this or id must be provided."),
      country: z.string().default("us").describe("Country code to get reviews from (default: us)"),
      page: z.number().min(1).max(10).default(1).describe("Page number to retrieve (default: 1, max: 10)"),
      sort: z.enum(["recent", "helpful"]).default("recent").describe("Sort order (recent or helpful)")
    }, 
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the return format (array of reviews with specific fields) but lacks critical behavioral details: it doesn't mention whether this is a read-only operation, if it requires authentication, rate limits, pagination behavior beyond the 'page' parameter, or error handling. The description is insufficient for a tool with 5 parameters and no annotation coverage.

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?

The description is appropriately sized and front-loaded with the core purpose. The bulleted list of return fields is well-structured and informative. However, the second sentence starting with 'Returns an array...' could be more concise, and the description lacks any concluding context about limitations or usage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (5 parameters, no output schema, no annotations), the description is partially complete. It clearly explains what the tool returns but doesn't address behavioral aspects like safety, performance, or error conditions. The absence of an output schema means the description must fully document return values, which it does adequately with the bulleted list, but other contextual gaps remain.

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?

The schema description coverage is 100%, so the schema already fully documents all 5 parameters. The description adds no parameter-specific information beyond what's in the schema (e.g., it doesn't clarify the relationship between 'id' and 'appId' or provide examples of valid country codes). This meets the baseline for high schema coverage but doesn't add extra value.

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?

The description clearly states the verb ('Get') and resource ('reviews for an App Store app'), making the purpose specific and unambiguous. It distinguishes from siblings like 'app-store-ratings' (which likely provides aggregated ratings) and 'app-store-details' (which provides app metadata) by focusing on individual review data.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention siblings like 'google-play-reviews' (for Android apps) or 'app-store-ratings' (for aggregated scores), nor does it specify prerequisites or use cases beyond the basic function. This leaves the agent without context for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JiantaoFu/AppInsightMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server