Skip to main content
Glama
MiguelAlvRed

Store Scraper MCP

by MiguelAlvRed

developer

Retrieve all applications published by a specific developer from app stores. Use this tool to analyze a developer's portfolio across iOS and Android platforms.

Instructions

Get all apps by a developer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
devIdYesiTunes artistId of the developer (e.g., 284882218 for Facebook)
countryNoTwo-letter country code (default: us)us
langNoLanguage code (default: en)en

Implementation Reference

  • The handler function that implements the core logic of the 'developer' tool: validates input, builds URL, fetches data from App Store, parses apps, and formats response.
    async function handleDeveloper(args) {
      try {
        const { devId, country = 'us', lang = 'en' } = args;
    
        if (!devId) {
          throw new Error('devId is required');
        }
    
        const url = buildDeveloperUrl({ devId, country, lang });
        const data = await fetchJSON(url);
        const apps = parseApps(data);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                developerId: devId,
                apps,
                count: apps.length,
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({ error: error.message }, null, 2),
            },
          ],
          isError: true,
        };
      }
    }
  • The input schema definition for the 'developer' tool, registered in ListToolsRequestSchema handler.
      name: 'developer',
      description: 'Get all apps by a developer',
      inputSchema: {
        type: 'object',
        properties: {
          devId: {
            type: 'number',
            description: 'iTunes artistId of the developer (e.g., 284882218 for Facebook)',
          },
          country: {
            type: 'string',
            description: 'Two-letter country code (default: us)',
            default: 'us',
          },
          lang: {
            type: 'string',
            description: 'Language code (default: en)',
            default: 'en',
          },
        },
        required: ['devId'],
      },
    },
  • Registration of the 'developer' tool handler in the switch statement of CallToolRequestSchema handler.
    case 'similar':
      return await handleSimilar(args);
  • Helper function to construct the iTunes lookup URL for developer apps, used by the 'developer' handler.
    export function buildDeveloperUrl(params) {
      const { devId, country = 'us', lang = 'en' } = params;
      const queryParams = new URLSearchParams({
        id: devId.toString(),
        country: country,
        lang: lang,
        entity: 'software',
      });
      
      return `${ITUNES_BASE}/lookup?${queryParams.toString()}`;
    }
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 states a read operation ('Get'), implying it's likely non-destructive, but doesn't mention any constraints like rate limits, authentication needs, pagination, or what the return format looks like. This is inadequate for a tool with parameters and no output schema.

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 a single, efficient sentence with zero wasted words, making it easy to parse and front-loaded with the core purpose. It earns its place by clearly stating what the tool does without unnecessary elaboration.

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

Completeness2/5

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

Given the tool has parameters and no output schema, the description is incomplete. It doesn't explain what 'all apps' entails (e.g., format, pagination, or limitations) or provide behavioral context. With no annotations and missing output details, it fails to compensate for the lack of structured information.

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 three parameters (devId, country, lang) with descriptions and defaults. The description adds no additional meaning beyond implying 'developer' relates to 'devId', which is already clear from the schema. This meets the baseline for high 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 'Get all apps by a developer' clearly states the verb ('Get') and resource ('apps by a developer'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'gp_developer' or 'search', which might have overlapping functionality, preventing 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 such as 'gp_developer', 'search', or 'list'. It lacks any context about prerequisites, exclusions, or comparative use cases, leaving the agent to infer usage from the tool name alone.

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/MiguelAlvRed/mobile-store-scraper-mcp'

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