Huawei App Gallery

update_language_info

Add or update localized app store listing details such as name, description, and release notes for a specified language on Huawei App Gallery.

Instructions

Add or update localized store listing (name, description, release notes) for a language.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lang": "<lang>"
    },
    "name": "update_language_info"
  }
}

Input Schema

Name	Required	Description
`app_id`	No	AppGallery Connect app ID. Optional if HUAWEI_APP_ID is set in the environment.
`lang`	Yes	BCP-47 tag, e.g. "en-US", "zh-CN".
`app_name`	No
`app_desc`	No
`brief_desc`	No
`new_features`	No	What's new / release notes.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Mar 24, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It does not specify if partial updates overwrite fields, if missing optional fields clear them, or if the operation affects app submission status. The 'add or update' duality is ambiguous without further detail.

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

Conciseness4/5

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

Single sentence is concise with no redundant text. However, it could be better structured with bullet points or explicit mapping of description terms to schema parameters.

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 output schema, no annotations, and 6 parameters, the description fails to provide return value details, idempotency info, or clarify the 'add vs update' behavior. Insufficient for safe and correct invocation.

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 coverage is 50% (3 of 6 params described). Description adds value by explaining some fields (name, description, release notes) but omits 'brief_desc'. It partially compensates for missing schema descriptions but is incomplete.

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

Purpose5/5

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

Description clearly states the verb ('Add or update'), resource ('localized store listing'), and specific fields (name, description, release notes). It effectively distinguishes from siblings like 'delete_language_info'.

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?

No guidance on when to use this tool vs siblings (e.g., 'delete_language_info', 'update_app_info'). Missing prerequisites or context for when 'add' vs 'update' behavior applies, which is critical for a dual-purpose tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server