Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

app-store-similar

Find similar apps on the App Store by providing an app ID or bundle ID to discover competitors and related applications for market research.

Instructions

Get similar apps ('customers also bought') from the App Store. Returns a list of apps with:

  • id: App Store ID number

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

  • title: App name

  • icon: Icon image URL

  • url: App Store URL

  • price: Price in USD

  • currency: Price currency code

  • free: Boolean indicating if app is free

  • description: App description

  • developer: Developer name

  • developerUrl: Developer's App Store URL

  • developerId: Developer's ID

  • genre: App category name

  • genreId: Category ID

  • released: Release 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.

Implementation Reference

  • The handler function for the "app-store-similar" tool. It takes id or appId, calls store.similar from the app-store-scraper library, and returns the results as JSON text content.
    async ({ id, appId }) => {
      const similar = await store.similar({ id, appId });
      return { content: [{ type: "text", text: JSON.stringify(similar) }] };
    }
  • Input schema defined using Zod, requiring either a numeric App Store ID or bundle ID (appId).
    {
      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.")
    }, 
  • src/server.js:150-175 (registration)
    Full registration of the "app-store-similar" tool on the MCP server, including name, description of output, input schema, and handler function.
    server.tool("app-store-similar", 
      "Get similar apps ('customers also bought') from the App Store. Returns a list of apps with:\n" +
      "- id: App Store ID number\n" +
      "- appId: Bundle ID (e.g. 'com.company.app')\n" +
      "- title: App name\n" + 
      "- icon: Icon image URL\n" +
      "- url: App Store URL\n" +
      "- price: Price in USD\n" +
      "- currency: Price currency code\n" +
      "- free: Boolean indicating if app is free\n" +
      "- description: App description\n" +
      "- developer: Developer name\n" +
      "- developerUrl: Developer's App Store URL\n" +
      "- developerId: Developer's ID\n" +
      "- genre: App category name\n" +
      "- genreId: Category ID\n" +
      "- released: Release 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.")
      }, 
      async ({ id, appId }) => {
        const similar = await store.similar({ id, appId });
        return { content: [{ type: "text", text: JSON.stringify(similar) }] };
      }
    );
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. While it clearly describes the return format (a list of apps with specific fields), it lacks critical behavioral information: whether this requires authentication, rate limits, pagination handling, error conditions, or what happens when neither id nor appId is provided (both are optional in schema). For a read operation with zero annotation coverage, this is insufficient.

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 in the first sentence. The bulleted list of return fields is necessary for clarity given no output schema, though it makes the description longer. Every element serves a purpose with minimal waste.

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 does well by documenting the return format in detail. However, it misses important contextual elements: authentication requirements, rate limits, error handling, and the implications of the optional parameters (what happens if neither is provided?). For a tool with 2 parameters and rich return data, this leaves gaps in operational understanding.

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%, with both parameters clearly documented in the schema itself (id as numeric App ID, appId as bundle ID, with 'either/or' requirement). The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline but doesn't provide 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 similar apps') and resource ('from the App Store'), with the parenthetical 'customers also bought' providing additional context. It explicitly distinguishes this tool from its sibling 'app-store-details' and 'app-store-search' by focusing on similarity recommendations rather than direct lookups or searches.

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

Usage Guidelines4/5

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

The description implies usage context by specifying it's for finding similar apps based on an existing app, which naturally distinguishes it from search or detail tools. However, it doesn't explicitly state when NOT to use this tool or name specific alternatives among the many siblings (like 'app-store-search' for broader queries).

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