Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

app-store-details

Retrieve comprehensive App Store app details including metadata, pricing, ratings, screenshots, and developer information for market research and analysis.

Instructions

Get detailed information about an App Store app. Returns an object with:

  • id: App Store ID number

  • appId: Bundle ID (e.g. 'com.company.app')

  • title: App name

  • url: App Store URL

  • description: Full app description

  • icon: Icon URL

  • genres: Array of category names

  • genreIds: Array of category IDs

  • primaryGenre: Main category name

  • primaryGenreId: Main category ID

  • contentRating: Content rating (e.g. '4+')

  • languages: Array of language codes

  • size: App size in bytes

  • requiredOsVersion: Minimum iOS version required

  • released: Initial release date (ISO string)

  • updated: Last update date (ISO string)

  • releaseNotes: Latest version changes

  • version: Current version string

  • price: Price in USD

  • currency: Price currency code

  • free: Boolean indicating if app is free

  • developerId: Developer's ID

  • developer: Developer name

  • developerUrl: Developer's App Store URL

  • developerWebsite: Developer's website URL if available

  • score: Current rating (0-5)

  • reviews: Total number of ratings

  • currentVersionScore: Current version rating (0-5)

  • currentVersionReviews: Current version review count

  • screenshots: Array of screenshot URLs

  • ipadScreenshots: Array of iPad screenshot URLs

  • appletvScreenshots: Array of Apple TV screenshot URLs

  • supportedDevices: Array of supported device IDs

  • ratings: Total number of ratings (when ratings option enabled)

  • histogram: Rating distribution by star level (when ratings option enabled)

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 app details from (default: us). Also affects data language.us
langNoLanguage code for result text. If not provided, uses country-specific language.
ratingsNoLoad additional ratings information like ratings count and histogram

Implementation Reference

  • The handler function that fetches detailed App Store app information using the store.app method from the app-store-scraper library and returns it as JSON-formatted text content.
      async ({ id, appId, country, lang, ratings }) => {
        const details = await store.app({ id, appId, country, lang, ratings });
        return { content: [{ type: "text", text: JSON.stringify(details) }] };
      }
    );
  • Zod schema defining the input parameters for the tool: optional id (number) or appId (string), country (default 'us'), optional lang, optional ratings (default false).
    {
      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 app details from (default: us). Also affects data language."),
      lang: z.string().optional().describe("Language code for result text. If not provided, uses country-specific language."),
      ratings: z.boolean().optional().default(false).describe("Load additional ratings information like ratings count and histogram")
    },
  • src/server.js:70-106 (registration)
    Registration of the 'app-store-details' tool using McpServer.tool(), including the tool name, detailed description of return fields, and parameters for schema and handler.
    server.tool("app-store-details", 
      "Get detailed information about an App Store app. Returns an object with:\n" +
      "- id: App Store ID number\n" +
      "- appId: Bundle ID (e.g. 'com.company.app')\n" +
      "- title: App name\n" +
      "- url: App Store URL\n" +
      "- description: Full app description\n" +
      "- icon: Icon URL\n" +
      "- genres: Array of category names\n" +
      "- genreIds: Array of category IDs\n" +
      "- primaryGenre: Main category name\n" +
      "- primaryGenreId: Main category ID\n" +
      "- contentRating: Content rating (e.g. '4+')\n" +
      "- languages: Array of language codes\n" +
      "- size: App size in bytes\n" +
      "- requiredOsVersion: Minimum iOS version required\n" +
      "- released: Initial release date (ISO string)\n" +
      "- updated: Last update date (ISO string)\n" +
      "- releaseNotes: Latest version changes\n" +
      "- version: Current version string\n" +
      "- price: Price in USD\n" +
      "- currency: Price currency code\n" +
      "- free: Boolean indicating if app is free\n" +
      "- developerId: Developer's ID\n" +
      "- developer: Developer name\n" +
      "- developerUrl: Developer's App Store URL\n" +
      "- developerWebsite: Developer's website URL if available\n" +
      "- score: Current rating (0-5)\n" +
      "- reviews: Total number of ratings\n" +
      "- currentVersionScore: Current version rating (0-5)\n" +
      "- currentVersionReviews: Current version review count\n" +
      "- screenshots: Array of screenshot URLs\n" +
      "- ipadScreenshots: Array of iPad screenshot URLs\n" +
      "- appletvScreenshots: Array of Apple TV screenshot URLs\n" +
      "- supportedDevices: Array of supported device IDs\n" +
      "- ratings: Total number of ratings (when ratings option enabled)\n" +
      "- histogram: Rating distribution by star level (when ratings option enabled)",
  • Import of the '@jeromyfu/app-store-scraper' library, which provides the store.app method used in the tool handler.
    import store from '@jeromyfu/app-store-scraper';
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It lists return fields but does not disclose behavioral traits such as rate limits, authentication needs, error handling, or data freshness. The mention of 'when ratings option enabled' hints at conditional behavior but lacks full transparency.

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?

The description is front-loaded with a clear purpose statement, but the extensive list of return fields (over 30 items) makes it verbose. While informative, this bulk could be streamlined or moved to an output schema if available, reducing clutter in the description.

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 complexity (5 parameters, no output schema, no annotations), the description is partially complete. It details return values extensively, which compensates for the lack of output schema, but misses behavioral context and usage guidelines. This leaves gaps for effective tool invocation.

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 parameters thoroughly. The description adds no parameter-specific information beyond what the schema provides, such as examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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 detailed information about an App Store app.' It specifies the verb ('Get') and resource ('App Store app'), but does not explicitly differentiate it from siblings like 'app-store-search' or 'app-store-developer', which likely have overlapping or related purposes.

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. With siblings like 'app-store-search' (likely for finding apps) and 'app-store-developer' (likely for developer info), there is no indication of context, prerequisites, or exclusions for using this detailed info tool.

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