Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

app-store-search

Search the Apple App Store to find apps by name, developer, or category. Retrieve detailed app information including pricing, descriptions, release dates, and developer data for market research and competitor analysis.

Instructions

Search for apps on the App Store. Returns a list of apps with the following fields:

  • 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
termYesSearch term (required)
numNoNumber of results to retrieve (default: 50)
pageNoPage of results to retrieve (default: 1)
countryNoTwo letter country code (default: us)us
langNoLanguage code for result text (default: en-us)en-us
idsOnlyNoSkip extra lookup request. Returns array of application IDs only (default: false)

Implementation Reference

  • The handler function that executes the app-store-search tool logic. It calls store.search with provided parameters and returns the results as a JSON string in MCP content format.
    async ({ term, num, page, country, lang, idsOnly }) => {
      const results = await store.search({ term, num, page, country, lang, idsOnly });
      return { content: [{ type: "text", text: JSON.stringify(results) }] };
    }
  • Zod schema defining the input parameters for the app-store-search tool.
    {
      term: z.string().describe("Search term (required)"),
      num: z.number().default(50).describe("Number of results to retrieve (default: 50)"),
      page: z.number().default(1).describe("Page of results to retrieve (default: 1)"),
      country: z.string().default("us").describe("Two letter country code (default: us)"),
      lang: z.string().default("en-us").describe("Language code for result text (default: en-us)"),
      idsOnly: z.boolean().default(false).describe("Skip extra lookup request. Returns array of application IDs only (default: false)")
  • src/server.js:39-68 (registration)
    Registration of the 'app-store-search' tool on the MCP server instance, including description, input schema, and inline handler.
    server.tool("app-store-search", 
      "Search for apps on the App Store. Returns a list of apps with the following fields:\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)",
      {
        term: z.string().describe("Search term (required)"),
        num: z.number().default(50).describe("Number of results to retrieve (default: 50)"),
        page: z.number().default(1).describe("Page of results to retrieve (default: 1)"),
        country: z.string().default("us").describe("Two letter country code (default: us)"),
        lang: z.string().default("en-us").describe("Language code for result text (default: en-us)"),
        idsOnly: z.boolean().default(false).describe("Skip extra lookup request. Returns array of application IDs only (default: false)")
      }, 
      async ({ term, num, page, country, lang, idsOnly }) => {
        const results = await store.search({ term, num, page, country, lang, idsOnly });
        return { content: [{ type: "text", text: JSON.stringify(results) }] };
      }
    );
  • Import of the external app store scraper library used by the app-store-search tool handler.
    import store from '@jeromyfu/app-store-scraper';
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 lists return fields but doesn't mention critical behaviors like rate limits, authentication requirements, error handling, or pagination details (beyond the 'page' parameter). For a search tool with 6 parameters, this is insufficient for reliable agent operation.

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: the first sentence states the purpose, followed by a structured list of return fields. There's no redundant information, though the list format is slightly verbose. Every sentence earns its place, making it efficient for agent comprehension.

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 (6 parameters, no output schema, no annotations), the description is partially complete. It covers the purpose and return format but lacks behavioral details (e.g., rate limits, errors) and usage guidelines relative to siblings. This is adequate for basic use but leaves gaps for robust agent operation.

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 fully documents all 6 parameters. The description adds no parameter-specific information beyond what's in the schema, but it does list the return fields, which provides context for interpreting results. This meets the baseline for high schema coverage.

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: 'Search for apps on the App Store.' It specifies the verb ('Search') and resource ('apps on the App Store'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'app-store-suggest' or 'google-play-search', which prevents a perfect score.

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 sibling tools like 'app-store-suggest' (for autocomplete suggestions) or 'google-play-search' (for Android apps), nor does it specify use cases or exclusions. This leaves the agent with minimal 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