Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

get_app_store_version_localization

Retrieve detailed localization data for a specific App Store version to manage app metadata across different languages and regions.

Instructions

Get detailed information about a specific app store version localization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localizationIdYesThe ID of the app store version localization

Implementation Reference

  • The core handler function that executes the tool logic. It validates the input, constructs the API endpoint, and calls the AppStoreConnectClient to fetch the specific app store version localization by ID.
    async getAppStoreVersionLocalization(args: {
      localizationId: string;
    }): Promise<AppStoreVersionLocalizationResponse> {
      const { localizationId } = args;
      
      validateRequired(args, ['localizationId']);
      
      return this.client.get<AppStoreVersionLocalizationResponse>(
        `/appStoreVersionLocalizations/${localizationId}`
      );
    }
  • Defines the MCP tool schema including the tool name, description, and input JSON schema specifying the required 'localizationId' parameter.
      description: "Get detailed information about a specific app store version localization",
      inputSchema: {
        type: "object",
        properties: {
          localizationId: {
            type: "string",
            description: "The ID of the app store version localization"
          }
        },
        required: ["localizationId"]
      }
    },
  • src/index.ts:1358-1359 (registration)
    Registers the tool in the MCP server's CallToolRequest handler by mapping the tool name to the execution of the LocalizationHandlers.getAppStoreVersionLocalization method.
    return { toolResult: await this.localizationHandlers.getAppStoreVersionLocalization(args as any) };
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 states this is a 'Get' operation, implying read-only access, but doesn't clarify authentication requirements, rate limits, error conditions, or response format. For a tool with zero annotation coverage, this leaves significant behavioral gaps unaddressed.

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 front-loads the core purpose without unnecessary words. Every element ('Get detailed information about a specific app store version localization') directly contributes to understanding the tool's function, with zero wasted content.

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 no annotations, no output schema, and a read operation with one parameter, the description is insufficiently complete. It doesn't explain what 'detailed information' includes, potential return values, or operational constraints. For a tool in this context, more behavioral and output context is needed to adequately guide an agent.

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 the single parameter 'localizationId' fully documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides (e.g., format examples, sourcing hints), so it meets the baseline for high schema coverage without compensating value.

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 detailed information about') and resource ('a specific app store version localization'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'list_app_store_version_localizations' or 'update_app_store_version_localization', which would require explicit comparison to achieve 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 prerequisites (e.g., needing a localization ID from another operation), contrast it with 'list_app_store_version_localizations' for bulk retrieval, or specify scenarios where detailed information is needed versus basic listing.

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