Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

app-store-ratings

Retrieve App Store ratings data including total ratings count and star distribution histogram for market analysis and competitor research.

Instructions

Get ratings for an App Store app. Returns an object with:

  • ratings: Total number of ratings

  • histogram: Distribution of ratings by star level (1-5)

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 ratings from (default: us)us

Implementation Reference

  • Handler function that calls store.ratings() with id/appId/country parameters and returns the ratings data as JSON-formatted text content.
    async ({ id, appId, country }) => {
      const ratings = await store.ratings({ id, appId, country });
      return { content: [{ type: "text", text: JSON.stringify(ratings) }] };
    }
  • Zod input schema defining optional id (number), appId (string), and country (string default 'us').
    {
      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 ratings from (default: us)")
    }, 
  • src/server.js:219-232 (registration)
    Full registration of the 'app-store-ratings' tool using server.tool(), including description, input schema, and inline handler function.
    server.tool("app-store-ratings", 
      "Get ratings for an App Store app. Returns an object with:\n" +
      "- ratings: Total number of ratings\n" +
      "- histogram: Distribution of ratings by star level (1-5)",
      {
        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 ratings from (default: us)")
      }, 
      async ({ id, appId, country }) => {
        const ratings = await store.ratings({ id, appId, country });
        return { content: [{ type: "text", text: JSON.stringify(ratings) }] };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It describes the return format (object with ratings count and histogram), which is helpful, but doesn't mention important behavioral aspects like whether this requires authentication, rate limits, error conditions, or whether the data is real-time or cached. The description adds some value but leaves significant gaps.

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?

The description is perfectly concise and well-structured. The first sentence states the core purpose, followed by a clear bulleted list of return values. Every sentence earns its place with no wasted words, and the information is front-loaded effectively.

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 no annotations and no output schema, the description provides basic return format information which is helpful. However, for a data retrieval tool with 3 parameters, it should ideally cover more behavioral context like authentication requirements, data freshness, or error handling. The description is minimally adequate but has clear gaps in completeness.

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%, so the schema already documents all three parameters thoroughly. The description doesn't add any parameter semantics beyond what's in the schema - it doesn't explain parameter relationships, provide examples beyond what's in schema descriptions, or clarify edge cases. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the tool's purpose: 'Get ratings for an App Store app' with specific verb ('Get') and resource ('ratings for an App Store app'). It distinguishes from some siblings like 'app-store-details' or 'app-store-reviews' by focusing on ratings data, but doesn't explicitly differentiate from all possible alternatives.

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?

No guidance is provided about when to use this tool versus alternatives. While the description implies this is for App Store ratings specifically, it doesn't mention when to choose this over similar tools like 'app-store-reviews' or 'google-play-ratings' (if such a tool existed), nor does it specify prerequisites or constraints beyond what's in the schema.

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