Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

update_app_store_version_localization

Modify app store listing details like description, keywords, or what's new text for specific language versions to keep store content current.

Instructions

Update a specific field in an app store version localization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localizationIdYesThe ID of the app store version localization to update
fieldYesThe field to update
valueYesThe new value for the field

Implementation Reference

  • The main handler function that performs the API call to update a specific field (description, keywords, etc.) in an App Store version localization using the AppStoreConnectClient. Includes input validation and field validation.
    async updateAppStoreVersionLocalization(args: {
      localizationId: string;
      field: AppStoreVersionLocalizationField;
      value: string;
    }): Promise<AppStoreVersionLocalizationResponse> {
      const { localizationId, field, value } = args;
      
      validateRequired(args, ['localizationId', 'field', 'value']);
      
      // Validate field
      const validFields: AppStoreVersionLocalizationField[] = [
        'description', 'keywords', 'marketingUrl', 
        'promotionalText', 'supportUrl', 'whatsNew'
      ];
      
      if (!validFields.includes(field)) {
        throw new Error(`Invalid field: ${field}. Must be one of: ${validFields.join(', ')}`);
      }
      
      const requestData: AppStoreVersionLocalizationUpdateRequest = {
        data: {
          type: 'appStoreVersionLocalizations',
          id: localizationId,
          attributes: {
            [field]: value
          }
        }
      };
      
      return this.client.patch<AppStoreVersionLocalizationResponse>(
        `/appStoreVersionLocalizations/${localizationId}`,
        requestData
      );
    }
  • Defines the tool schema including name, description, and inputSchema with properties for localizationId, field (enum), and value, as returned in listTools.
    {
      name: "update_app_store_version_localization",
      description: "Update a specific field in an app store version localization",
      inputSchema: {
        type: "object",
        properties: {
          localizationId: {
            type: "string",
            description: "The ID of the app store version localization to update"
          },
          field: {
            type: "string",
            enum: ["description", "keywords", "marketingUrl", "promotionalText", "supportUrl", "whatsNew"],
            description: "The field to update"
          },
          value: {
            type: "string",
            description: "The new value for the field"
          }
        },
        required: ["localizationId", "field", "value"]
      }
    },
  • src/index.ts:1360-1361 (registration)
    Registers the tool by mapping the tool name to the call of the handler method in the MCP server's CallToolRequest handler switch statement.
    case "update_app_store_version_localization":
      return { toolResult: await this.localizationHandlers.updateAppStoreVersionLocalization(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 it's an update operation, implying mutation, but doesn't cover critical aspects like required permissions, whether changes are reversible, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 action ('update') and resource. There's zero waste—every word contributes directly to stating the tool's purpose without redundancy or fluff.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., side effects, error handling), usage context, and expected outcomes. While concise, it doesn't compensate for the missing structured data, leaving the agent with insufficient guidance for safe and effective use.

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 all three parameters well-documented in the schema (localizationId, field with enum values, value). The description adds no additional parameter semantics beyond what's in the schema, such as formatting examples or constraints. 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 ('update') and resource ('a specific field in an app store version localization'), making the purpose unambiguous. It distinguishes itself from siblings like 'get_app_store_version_localization' by specifying it's an update operation rather than a retrieval. However, it doesn't explicitly differentiate from other update-like tools that might exist in the broader context.

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 an existing localization), exclusions (e.g., which fields cannot be updated), or related tools like 'create_app_store_version' or 'list_app_store_version_localizations' for context. Usage is implied through the action but not explicitly framed.

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