Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_app_store_version_localizations

Retrieve all language-specific metadata for an App Store version to manage localized app store listings and descriptions.

Instructions

Get all localizations for a specific app store version

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appStoreVersionIdYesThe ID of the app store version
limitNoMaximum number of localizations to return (default: 100)

Implementation Reference

  • The core handler function that validates the input parameters and makes an authenticated GET request to the App Store Connect API endpoint '/appStoreVersionLocalizations' to retrieve the list of localizations for the specified app store version.
    async listAppStoreVersionLocalizations(args: {
      appStoreVersionId: string;
      limit?: number;
    }): Promise<ListAppStoreVersionLocalizationsResponse> {
      const { appStoreVersionId, limit = 100 } = args;
      
      validateRequired(args, ['appStoreVersionId']);
      
      const params: Record<string, any> = {
        limit: sanitizeLimit(limit),
        'filter[appStoreVersion]': appStoreVersionId
      };
      
      return this.client.get<ListAppStoreVersionLocalizationsResponse>(
        '/appStoreVersionLocalizations',
        params
      );
    }
  • Defines the tool's name, description, and input schema for validation in the MCP tool list.
      name: "list_app_store_version_localizations",
      description: "Get all localizations for a specific app store version",
      inputSchema: {
        type: "object",
        properties: {
          appStoreVersionId: {
            type: "string",
            description: "The ID of the app store version"
          },
          limit: {
            type: "number",
            description: "Maximum number of localizations to return (default: 100)",
            minimum: 1,
            maximum: 200
          }
        },
        required: ["appStoreVersionId"]
      }
    },
  • src/index.ts:1354-1355 (registration)
    Registers the tool by mapping incoming tool calls with name 'list_app_store_version_localizations' to the appropriate handler method on the LocalizationHandlers instance.
    case "list_app_store_version_localizations":
      return { toolResult: await this.localizationHandlers.listAppStoreVersionLocalizations(args as any) };
  • TypeScript interface defining the structure of the API response from listing app store version localizations.
    export interface ListAppStoreVersionLocalizationsResponse {
      data: AppStoreVersionLocalization[];
      links?: {
        self: string;
        next?: string;
      };
      meta?: {
        paging: {
          total: number;
          limit: number;
        };
      };
    }
  • src/index.ts:81-82 (registration)
    Instantiates the LocalizationHandlers class with the AppStoreConnectClient, making the handler methods available for tool registration.
    this.localizationHandlers = new LocalizationHandlers(this.client);
    this.workflowHandlers = new WorkflowHandlers(this.client);
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 this is a 'Get' operation (implying read-only), but doesn't mention pagination behavior, rate limits, authentication requirements, error conditions, or what format the localizations are returned in. For a list operation with zero annotation coverage, this leaves significant behavioral gaps.

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 that states the core purpose without unnecessary words. It's appropriately sized for a simple list operation and front-loads the essential information.

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 list operation with good schema coverage but no annotations and no output schema, the description is minimally adequate. It states what the tool does but lacks important context about return format, pagination, and differentiation from similar tools. The absence of output schema means the agent won't know what structure to expect from the response.

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 well-documented in the schema. The description doesn't add any meaningful parameter semantics beyond what's already in the schema (e.g., it doesn't explain what an 'app store version' is or provide context about localization types). Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('Get') and resource ('all localizations for a specific app store version'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'get_app_store_version_localization' (singular vs. plural), which could cause confusion about when to use each tool.

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 like 'get_app_store_version_localization' or 'list_app_store_versions'. It doesn't mention prerequisites, context for usage, or any exclusions, leaving the agent to infer usage patterns from tool names 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/concavegit/app-store-connect-mcp-server'

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