Skip to main content
Glama
appreply-co

mcp-appstore

by appreply-co

search_app

Search for apps on iOS and Android app stores by term, platform, and region to find relevant applications and their details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesThe search term to look up (e.g., 'panda', 'spotify', 'photo editor'). This is required.
platformYesThe platform to search on ('ios' for Apple App Store, 'android' for Google Play Store).
numNoNumber of results to return (1-250, default 10). For Android max is 250, for iOS typically defaults to 50.
countryNoTwo-letter country code for the App Store/Play Store region (e.g., 'us', 'de', 'gb'). Affects ranking and availability. Default 'us'.us

Implementation Reference

  • The core handler function for the 'search_app' tool. It takes search parameters, queries the appropriate store API (Google Play via gplay or App Store via app-store-scraper), standardizes the app results across platforms, and returns formatted JSON with search results or error information.
    async ({ term, platform, num, country }) => {
      try {
        let results;
        
        if (platform === "android") {
          // Search on Google Play Store
          results = await memoizedGplay.search({
            term,
            num,
            country,
            fullDetail: false
          });
          
          // Standardize the results
          results = results.map(app => ({
            id: app.appId,
            appId: app.appId,
            title: app.title,
            developer: app.developer,
            developerId: app.developerId,
            icon: app.icon,
            score: app.score,
            scoreText: app.scoreText,
            price: app.price,
            free: app.free,
            platform: "android",
            url: app.url
          }));
        } else {
          // Search on Apple App Store
          results = await memoizedAppStore.search({
            term,
            num,
            country
          });
          
          // Standardize the results
          results = results.map(app => ({
            id: app.id.toString(),
            appId: app.appId,
            title: app.title,
            developer: app.developer,
            developerId: app.developerId,
            icon: app.icon,
            score: app.score,
            price: app.price,
            free: app.free === true,
            platform: "ios",
            url: app.url
          }));
        }
        
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({
              query: term,
              platform,
              results,
              count: results.length
            }, null, 2)
          }]
        };
      } catch (error) {
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({
              error: error.message,
              query: term,
              platform
            }, null, 2)
          }],
          isError: true
        };
      }
    }
  • Zod input schema defining parameters for the search_app tool: term (required string), platform (ios/android), num (optional number 1-250 default 10), country (optional 2-letter code default 'us'). Validates and types tool arguments.
    {
      term: z.string().describe("The search term to look up (e.g., 'panda', 'spotify', 'photo editor'). This is required."),
      platform: z.enum(["ios", "android"]).describe("The platform to search on ('ios' for Apple App Store, 'android' for Google Play Store)."),
      num: z.number().min(1).max(250).optional().default(10).describe("Number of results to return (1-250, default 10). For Android max is 250, for iOS typically defaults to 50."),
      country: z.string().length(2).optional().default("us").describe("Two-letter country code for the App Store/Play Store region (e.g., 'us', 'de', 'gb'). Affects ranking and availability. Default 'us'.")
    },
  • server.js:58-143 (registration)
    The registration of the 'search_app' tool on the McpServer instance using server.tool(name, inputSchema, handlerCallback). This adds the tool to the MCP server's capabilities.
    server.tool(
      "search_app",
      {
        term: z.string().describe("The search term to look up (e.g., 'panda', 'spotify', 'photo editor'). This is required."),
        platform: z.enum(["ios", "android"]).describe("The platform to search on ('ios' for Apple App Store, 'android' for Google Play Store)."),
        num: z.number().min(1).max(250).optional().default(10).describe("Number of results to return (1-250, default 10). For Android max is 250, for iOS typically defaults to 50."),
        country: z.string().length(2).optional().default("us").describe("Two-letter country code for the App Store/Play Store region (e.g., 'us', 'de', 'gb'). Affects ranking and availability. Default 'us'.")
      },
      async ({ term, platform, num, country }) => {
        try {
          let results;
          
          if (platform === "android") {
            // Search on Google Play Store
            results = await memoizedGplay.search({
              term,
              num,
              country,
              fullDetail: false
            });
            
            // Standardize the results
            results = results.map(app => ({
              id: app.appId,
              appId: app.appId,
              title: app.title,
              developer: app.developer,
              developerId: app.developerId,
              icon: app.icon,
              score: app.score,
              scoreText: app.scoreText,
              price: app.price,
              free: app.free,
              platform: "android",
              url: app.url
            }));
          } else {
            // Search on Apple App Store
            results = await memoizedAppStore.search({
              term,
              num,
              country
            });
            
            // Standardize the results
            results = results.map(app => ({
              id: app.id.toString(),
              appId: app.appId,
              title: app.title,
              developer: app.developer,
              developerId: app.developerId,
              icon: app.icon,
              score: app.score,
              price: app.price,
              free: app.free === true,
              platform: "ios",
              url: app.url
            }));
          }
          
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({
                query: term,
                platform,
                results,
                count: results.length
              }, null, 2)
            }]
          };
        } catch (error) {
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({
                error: error.message,
                query: term,
                platform
              }, null, 2)
            }],
            isError: true
          };
        }
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/appreply-co/mcp-appstore'

If you have feedback or need assistance with the MCP directory API, please join our Discord server