Skip to main content
Glama
JiantaoFu

App Market Intelligence MCP

app-store-developer

Retrieve all apps published by a specific developer on the Apple App Store. Use this tool to research developer portfolios, analyze competitor offerings, and gather market intelligence for mobile app strategy.

Instructions

Get apps by a developer on 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
devIdYesiTunes artist ID of the developer (e.g., 284882218 for Facebook)
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.

Implementation Reference

  • Inline async handler function that invokes store.developer from the app-store-scraper library to fetch apps by developer and formats the response as MCP content.
    async ({ devId, country, lang }) => {
      const apps = await store.developer({ devId, country, lang });
      return { content: [{ type: "text", text: JSON.stringify(apps) }] };
    }
  • Zod schema defining input parameters for the tool: devId (required string), country (string, default 'us'), lang (optional string).
    {
      devId: z.string().describe("iTunes artist ID of the developer (e.g., 284882218 for Facebook)"),
      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.")
    }, 
  • src/server.js:178-204 (registration)
    Registration of the MCP tool using McpServer.tool(), including name, description, input schema, and inline handler function.
    server.tool("app-store-developer", 
      "Get apps by a developer on 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)",
      {
        devId: z.string().describe("iTunes artist ID of the developer (e.g., 284882218 for Facebook)"),
        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.")
      }, 
      async ({ devId, country, lang }) => {
        const apps = await store.developer({ devId, country, lang });
        return { content: [{ type: "text", text: JSON.stringify(apps) }] };
      }
    );
  • Import of the app-store-scraper library, providing the store.developer method used by 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?

With no annotations provided, the description carries full burden for behavioral disclosure. It describes the return format well but doesn't mention important behavioral aspects like whether this is a read-only operation, potential rate limits, authentication requirements, error conditions, or pagination behavior for large result sets.

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 structured: a clear purpose statement followed by a bulleted list of return fields. Every sentence earns its place, with zero wasted words. The bullet format makes return values easily scannable.

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?

For a read-only query tool with 3 parameters and no output schema, the description adequately covers the purpose and return format. However, it lacks important contextual information about behavioral constraints (rate limits, authentication), error handling, and how it differs from sibling tools, which would be needed for optimal agent usage.

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 fully documents all three parameters. The description doesn't add any additional parameter semantics beyond what's in the schema. This meets the baseline 3 score when schema does the heavy lifting.

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 specific action ('Get apps by a developer') and resource ('on the App Store'), with a detailed list of returned fields. It distinguishes from siblings like app-store-search (general search) and app-store-details (single app details) by focusing on developer-specific retrieval.

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

Usage Guidelines3/5

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

The description implies usage context (when you want apps from a specific developer), but doesn't explicitly state when to use this tool versus alternatives like app-store-search (for keyword searches) or app-store-developer (Google Play equivalent). No explicit exclusions or prerequisites are provided.

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